-
Notifications
You must be signed in to change notification settings - Fork 113
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
Sync times have regressed significantly since Ignition launch #2062
Comments
I followed this up on the rageshake and I inspected startup network traffic but there's nothing that points at anything having slowed down client/sdk side. There was a problem in a previous key backup implementation re startup request that but that has since been fixed. |
so where is the slowdown coming from in the rageshake? i'm seeing it reliably on every launch. |
There were 2 similar rageshakes, I commented on the other one here https://github.com/vector-im/element-x-ios-rageshakes/issues/1074#issuecomment-1810069242 tl;dr; app starts sync -> 2 seconds later sync comes back with 594kiB(!) of data -> takes 1 second to process rust side, app finally gets it |
this is still markedly slower than in sept |
Seeing ~4 sec here as well. Seems to happen to me when the app has been in the background for a while. Submitted logs referencing this issue. edit: Today I had a sync that took almost 10 seconds! Submitted another set of logs. |
this has totally changed with the move to SSS. it’s still not as fast as it could be, but it’s faster than it was. element-hq/synapse#17722 might also contribute to perf problems. keeping this open as it’s still way slower than the original launch. |
Steps to reproduce
Kegan has dug into a rageshake, and is seeing an inexplicable 3s gap in clientside logs (see rageshake for details). This behaviour started at some point in the last month or so - perhaps when backup got added?
The regression hasn't been picked up by the perftest jig.
Outcome
What did you expect?
Instant sync
What happened instead?
Sync regressing.
Your phone model
No response
Operating system version
No response
Application version
433
Homeserver
No response
Will you send logs?
Yes
The text was updated successfully, but these errors were encountered: