Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve UI when re-syncing an out of date client #9198

Open
ara4n opened this issue Mar 17, 2019 · 5 comments
Open

Improve UI when re-syncing an out of date client #9198

ara4n opened this issue Mar 17, 2019 · 5 comments
Labels
A-Performance O-Occasional Affects or can be seen by some users regularly or most users rarely S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Enhancement X-Needs-Design

Comments

@ara4n
Copy link
Member

ara4n commented Mar 17, 2019

it just took about 10 minutes for an incremental sync to return on my main account when firing up a client i hadn't used in a few months. surely incremental sync should be faster given it's dropping most of the data?

@bwindels
Copy link
Contributor

any indication whether or not this was client or server-side? E.g. could you see how long the request took in the network tab?

@lampholder lampholder added T-Defect A-Performance P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround labels Mar 18, 2019
@turt2live
Copy link
Member

It's server side, and has always been slow in this scenario.

@bwindels
Copy link
Contributor

Should we track this on the synapse side then? I suppose this is not matrix-org/synapse#3880 as that's for initial sync?

@Half-Shot
Copy link
Member

I'm actually finding this to be a problem for just 24 hours of inactivity. Obviously this is a condition of having a large account.

Probably what's missing from this issue is that the client's UX while it's trying to do the first incremental sync is quite poor. The room list doesn't render, and the client is full of blank spaces waiting for data. The displayname in the top left is an mxid. Overall, it's not clear to me why we don't just show a spinner while waiting for the first sync, as we do with initial syncs.

@novocaine novocaine added S-Critical Prevents work, causes data loss and/or has no workaround O-Uncommon Most users are unlikely to come across this or unexpected workflow and removed S-Major Severely degrades major functionality or product features, with no satisfactory workaround labels Aug 5, 2021
@novocaine novocaine changed the title /sync takes *forever* to return if you fire up an old matrix client UI should be incrementally available during long sync Aug 25, 2021
@novocaine
Copy link
Contributor

I'm actually finding this to be a problem for just 24 hours of inactivity. Obviously this is a condition of having a large account.

Probably what's missing from this issue is that the client's UX while it's trying to do the first incremental sync is quite poor. The room list doesn't render, and the client is full of blank spaces waiting for data. The displayname in the top left is an mxid. Overall, it's not clear to me why we don't just show a spinner while waiting for the first sync, as we do with initial syncs.

Agree. EW can't fix slow sync, but we should work out if the UI can be make as available as possible while the sync operation is in progress.

@novocaine novocaine added S-Major Severely degrades major functionality or product features, with no satisfactory workaround and removed S-Critical Prevents work, causes data loss and/or has no workaround labels Aug 25, 2021
@novocaine novocaine added O-Occasional Affects or can be seen by some users regularly or most users rarely and removed P1 O-Uncommon Most users are unlikely to come across this or unexpected workflow labels Nov 9, 2021
@novocaine novocaine changed the title UI should be incrementally available during long sync Improve UI when re-syncing an out of date client Nov 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Performance O-Occasional Affects or can be seen by some users regularly or most users rarely S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Enhancement X-Needs-Design
Projects
None yet
Development

No branches or pull requests

8 participants