-
Notifications
You must be signed in to change notification settings - Fork 212
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
The first synchronization is very slow. Is there any optimization strategy? #561
Comments
Yes, we are currently working on improving the initial sync (time & data usage): element-hq/element-ios#1931. This significantly improves the initial sync time if you are in rooms with thousands of users. |
You didn't understand what I meant. |
Just optimizing the processing speed of the pulled data does not greatly improve this time. |
Could you please define
There is no optimisation in response processing. There is just less data to process in the response. Room members lazy loading implies changes in both Matrix server and Matrix client. |
@Haley-Wong, as you are the 1st to identify this problem, could you also send some logs that demonstrate this exponential slowness issue, please? |
LL is released now |
I have an account, there are more than 1000 rooms, written after re-installation, initialization synchronization, to perform more than 10 minutes, how to optimize this problem?
I did a test. When there are 100 rooms, the initialization synchronization is about 5 seconds. When there are 600 rooms, the initialization synchronization is about 30 seconds. When there are 1100 rooms, the initialization synchronization is about 10 minutes. . When the number of rooms increases, the initial synchronization will be exponentially long. Should you consider how to optimize this time?
The text was updated successfully, but these errors were encountered: