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

The first synchronization is very slow. Is there any optimization strategy? #561

Closed
Haley-Wong opened this issue Sep 11, 2018 · 6 comments
Closed
Labels
support Support request

Comments

@Haley-Wong
Copy link

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?

@manuroe
Copy link
Contributor

manuroe commented Sep 11, 2018

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.

@manuroe manuroe added the support Support request label Sep 11, 2018
@Haley-Wong
Copy link
Author

You didn't understand what I meant.
I am not referring to initializing sync. The processing after pulling back the data is slow. I mean initializing the sync. This network request is very slow.Moreover, the time spent on this network request grows exponentially with the number of rooms.

@Haley-Wong
Copy link
Author

Just optimizing the processing speed of the pulled data does not greatly improve this time.

@manuroe
Copy link
Contributor

manuroe commented Sep 17, 2018

Could you please define initialization synchronization if it is not the initial sync?
More interestingly, as this question is posted in the matrix-ios-sdk and should be low level, what steps do you put in there (homeserver response time, response processing, time for data to be ready to use by the app, ...)

Just optimizing the processing speed of the pulled data does not greatly improve this time.

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.

@manuroe
Copy link
Contributor

manuroe commented Sep 18, 2018

When the number of rooms increases, the initial synchronization will be exponentially long.

@Haley-Wong, as you are the 1st to identify this problem, could you also send some logs that demonstrate this exponential slowness issue, please?

@manuroe
Copy link
Contributor

manuroe commented Dec 6, 2018

LL is released now

@manuroe manuroe closed this as completed Dec 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support Support request
Projects
None yet
Development

No branches or pull requests

2 participants