-
Notifications
You must be signed in to change notification settings - Fork 667
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
Desktop client uses over 100% CPU when syncing, slowing desktop to crawl #735
Comments
Please follow https://github.com/owncloud/mirall/blob/master/CONTRIBUTING.md when reporting bugs. |
Which packages are you using? |
Sorry for reporting "out of order." I'm using ownCloud Desktop 1.3.0, Built from Git revision 7cd2f3 on Jun 25 2013, 14:18:28 |
Ok, so what were you doing? Initial sync? Or have you been syncing data before? How much data are you syncing? |
I can confirm to this. My environment is: The syncing of 16 GB is finished successfully, but top shows nearly every time a cpu load of more or less 100% (2 core cpu). And I hear my computer working all the time. In the sync status window I can see that the client is connected but reconnects always after some seconds. |
This is not a fresh sync and total data in the folder is no more than 1GB. It's important to note ownCloud is not constantly over 100%, it just seems to peak there on a consistent basis. |
ownCloud Desktop 1.30, OCsync 0.80.0 (Git 7cd2f3) I got 100% CPU problem too, but not when files had changed. It comes sometime that owncloud goes to 100% CPU for eternity. I kill it, then relaunch and all come back fine. |
Any movement on this? |
I "solved" the problem for me according to this discussion: and added in .local/share/data/ownCloud/owncloud.cfg the two lines localPollinterval=600000 After doing this the cpu usage is in normal range. |
Interesting "fix," although--as I know you realize--it doesn't solve the B.Moore On Tue, Jul 23, 2013 at 10:32 AM, heribertius notifications@github.comwrote:
|
I added a patch to csync that improves the database access as that is a huge factor for an ordinary sync. Could you please try a nightly build and see if that improves the situation? |
Sure... Where are the nightlies? On Tuesday, July 23, 2013, dragotin wrote:
B.Moore |
I spoke too soon... the addition of the two lines about polling interval to the config file does not fix the CPU problem. |
Hi I have been testing the client on windows. I have a folder that I normally sync with Unison across 4 computers. So i thought I would use OC client to test that case. So far the client uses %50 cpu at all times non stop. I had some issues issues about failing csyinc client error but Iw as able to fix that with changing the client configs (found it throught he forums) max_time_difference = 10 max_depth = 50 The folder has 70.000 files totaling around 12gb. I can see that cpu use would be intense during the sync however seeing that the cpu use never goes down below %50 (on a quad core) sounds wrong to me. At this point as an easy fix I could recommend manual sycning so that the client does try to sync at all times constantly until the programmers can find a better solution for large repos. the client is windows 1.3 (win7 64) thanks |
You can try with 1.4 beta: it is available at the bottom of the page: http://owncloud.org/sync-clients/#testing |
All the 1.4 beta does is hang on "Calculating quota..." and reports "Unknown status." |
Now the 1.4 beta runs on my Linux Mint 13 XFCE. But it eats more than 100% CPU until I added the two lines from my post above in owncloud.cfg. Now it starts only some time with 100% CPU and in this time the config window "hangs". Very bothering is the exclamation mark in the status symbols when files from the exclude list are found. The given list can only be changed in the file "/etc/ownCloud/sync-exclude.lst". It takes some time until I found this. Where has the possibilty to renew the databases gone? I hope this issues can be fixed soon. Thank you. |
The 1.4 rc1 runs much better. The CPU usage now is in normal range and I have deleted the two additional lines in owncloud.cfg. Thank you for your work. |
On an elementaryOS beta2 desktop, which uses Ubuntu Precise repos in addition to elementary's own, the ownCloud desktop client uses over 100% of CPU when syncing according to "top" from the CLI. I'm sure that's not intended.
The text was updated successfully, but these errors were encountered: