Element-web: /sync takes *forever* to return if you fire up an old matrix client
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?
ara4n
All 4 comments
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?
bwindels
on 18 Mar 2019
It's server side, and has always been slow in this scenario.
turt2live
on 18 Mar 2019
Should we track this on the synapse side then? I suppose this is not https://github.com/matrix-org/synapse/issues/3880 as that's for initial sync?
bwindels
on 20 Mar 2019
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.
Half-Shot
on 19 Jul 2020
Related issues
niedzielski
路
3Comments
n-o-o-b
路
3Comments
PureTryOut
路
3Comments
turt2live
路
3Comments
NotAFile
路
3Comments
Most helpful comment
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.