-
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
[OSX] CPU usage #2990
Comments
@stonerl which version did you use? |
Sorry I just forgot to tell. 1.8.0 (Build 2139) |
Do you use any specific external storage on your server? |
@guruz No, just a plain vServer with:
And if needed, my Client Specs:
|
I think I figured out where the cpu usage comes from. I don't use one ownCloud folder to sync, I have configured four: Documents, Videos, Music, Pictures. After I removed three of the them from sync, the CPU Time after 20 Minutes where only 23 seconds. I'm going to test this further, but so far the more folders are configured the more cpu is used. |
So it is as I suspected. I returned to my usual configuration with 6 folders and CPU Time went up to 2 minutes after 20 minutes. So as I stated before, the more folders are configured, the higher the CPU usage. |
btw. maybe this one here is related #2993. |
@stonerl I think the logfile could help here to find out what re-triggers the sync to be launched https://raw.githubusercontent.com/owncloud/client/master/issue_template.md |
@guruz the logfile can be found here: https://kumori.fosuta.org/public.php?service=files&t=837aa204dfc0f0b0d332b03aa39764ef I ran ownCloud for about 5 minutes. |
In your log I can see the last I wonder what would then use the CPU? I don't see anything in the log which would cause a lot of CPU. CC @ckamm @jturcotte |
I just traced ownclout once again and looked in the logfile. As I said before the high cpu usage appears every 30 seconds so I think it gets invoked with this:
|
Could I ask you to try this nightly build: http://download.owncloud.com/desktop/daily/ownCloud-1.8.0.2204-nightly20150325.pkg ? |
@guruz I tried the nightly build but no improvement. CPU Time with 1.8.0: 57.27 and with the nightly: 57.22. But, I think I figured out where the usage comes from. First of all, from the above numbers one has to subtract about 20 seconds because during the first 40-50 seconds after starting ownCloud the program puts everything in place. So the net CPU time would be ~37 seconds. As I stated before I believe that is has something to do with the Etag polling: So i did the following: I removed my 6 sync-folders and created 6 empty folders (named 1 to 6) and added them to ownCloud. I left the folder empty just make sure that it would not be the amount of Etag that cause the cpu usage (my Images-folder for example has several hundred of Etags). I started my measurement again and came up with this numbers: 43.11 in total minus 6.6 for the startup, means a net CPU Time of ~37 seconds. I do believe that the server requests generate the cpu usage.
|
Just forgot to mention. Every run took exactly 10 minutes. |
This one has the commit above ^^ |
This solved the bug. While idling oc doesn't use any CPU at all. |
Thanks for the Analysis! |
@guruz Your're welcome! |
While using the Activity Monitor I just observed that ownCloud sometimes kicked in with a CPU usage of round about 50%. So I traced the behavior with Xcode and there I could see that every 30 seconds ownCloud uses allot of CPU for about 3 seconds. After 20 minutes the total CPU Time was: 1:11.70125. In comparison, dropbox was started a mere second before ownCloud and at the end of my measurement had a CPU Time of only 8.911494.
I uploaded the tracefile to my server, if needed you can find it here:
https://kumori.fosuta.org/public.php?service=files&t=611b8b351a755e965f824fda08ffddad
I don't know if this is anyhow related to #2937
The text was updated successfully, but these errors were encountered: