[Arathorn]

Fixing this has been the primary focus of the core Matrix team over the last year - we revealed the end result at FOSDEM a few weeks ago, and it literally improves performance to be better than Telegram/Discord/Slack or anything else we've benchmarked against: https://youtu.be/eUPJ9zFV5IE?t=566

If you're feeling adventurous, try develop.element.io and enable Sliding Sync in Labs, and you should get instant login, sync, and orders of magnitude better performance (but it is definitely beta). You may need to run your own SS proxy, for which we published a guide yesterday: https://youtu.be/25wkV2ZCSsM

[3np]

Thanks for the follow-up.

Unfortunately, those are all orthogonal: you are referring to server and client-server-sync performance. I'm referring to opening and navigating the client UI, and these issues are as present when offline and no homeserver communication and syncing is involved.

The developments you mention are all important, great, and exciting but from what I've seen so far the UI performance issues are unaddressed. We had users try to report these issues on GH historically but they tended to get dismissed as "can't reproduce on my mac" or left unattended.

[Arathorn]

for the sake of completeness: they aren’t orthogonal. the reason that element web can take tens of seconds to launch is not just because it’s syncing with the server, but because it is loading hundreds of MB of json from indexeddb. Sliding Sync fundamentally changes that; in fact the sliding sync impl I pointed you at doesn’t persist any local state in indexeddb between launches (element web has never supported launching offline, fwiw). Therefore time to launch and load the UI is immeasurably improved.