-
Notifications
You must be signed in to change notification settings - Fork 668
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
Discovering really slow #4324
Comments
You are using OS X? Did you let the discovery run through completely? In general, only the initial discovery will take some time. |
Hi Guruz, Yes, I let the discovery run through, after that it started syncing (it appeared that syncing itself was slower in this version, like what was reported in #3510). I've aborted syncing to start up with the logfile. I know that it is only the initial discovery, but everytime I make a change on the shared disk (for example adding a shared folder with a new user group), it starts syncing all the clients entirely from the start. This causes a lot of problems (around 10 users) Furthermore, sometimes during the discovery time something goes wrong (e.g. connection problem) and it starts from the beginning again. |
For measuring the request time I meant the sequences which look like this:
I think you pasted from the local discovery.
|
@MarcGro Also if you use the latest server version make sure to have the correct locking app and Redis configured. |
ok thank you. We haven't got time to look at it, but we definitely will |
Whats the version of the owncloud server? I suspect this is simply due to the server being slow. |
ok, let's have this reopen if there is more info |
Hi,
discovering changes is really slow. It takes about 1 or 2 hours for 6Gb of data. I've looked here:
#3510
and installed the last version Versie 2.1.1-nightly20151229 (build 2996), but it is still slow. It takes a few seconds for every folder to scan, also if there are only a few documents in a folder.
Does caching on the server help? I'll have to check, I don't think caching is enabled at the moment. Any other solutions?
thanks
Marc
The text was updated successfully, but these errors were encountered: