Abusive CPU Usage

[Doooooo0o]

Expected behaviour

Not using 100% CPU from 2 cores all the time while there is no sync

Actual behaviour

The exact opposite

Steps to reproduce

1. Fedora 23
2. Owncloud client latest
3. htop

Server configuration

Operating system:
Fedora23
Web server:
Nginx
Database:
Mariadb
PHP version:
5.6
ownCloud version:
Latest
Storage backend:
filesystem

Client configuration

Client version:

libowncloudsync0-2.2.0-9.1.x86_64
owncloud-client-2.2.0-9.1.x86_64
owncloud-client-l10n-2.2.0-9.1.x86_64

Operating system:
Fedora23
OS language:
Fr
Installation path of client:
/usr/bin/owncloud

[FlorentCoppint]

same thing on Ubuntu 16.04, owncloud process taking 100% of 1 core...

[bhcopeland]

yup, same issue here. (on laptop and desktop)

Arch Linux
2.2.0

[prairietree]

I do not want to abuse this comment, but I typed up all this information before I found this similar issue open. In addition to what is mentioned here I am also having excessive ram usage after a while of running ownCloud client.

Expected behaviour

OwnCloud Linux client maintains it cpu and ram usage so as to keep the system responsive.

Actual behaviour

On a large new sync 40 GB of mostly pictures cpu usage stayed at 90+%, and ram usage will eventually start climbing tell the system is unresponsive.

Steps to reproduce

1. Install the latest linux owncloud client on Kubuntu 16.04 or 14.04.
2. Try to sync 40 or so GB of mostly pictures.

Server configuration

Operating system: Ubuntu server 14.04

Web server: Apache

Database: MySql

PHP version:

ownCloud version: 9.0.1

Storage backend:

Client configuration

Client version: "Version 2.2.0%nil (build 1605)."

Operating system: Linux Kubuntu 16.04

OS language: English

Installation path of client: /usr/bin/owncloud

Logs

1. Output of owncloud --logwindow or owncloud --logfile log.txt

I will try to rerun it latter with logging enabled. I did not know I needed to enable it.

1. Web server error log:
2. ownCloud log (data/owncloud.log):

The story

I am having trouble with high cpu usage when running own cloud client on Kubuntu. I was having the same trouble with Kubuntu 14.04 so I upgraded to Kubuntu 16.04 last week, and installed the latest ownCloud client. After I added two syncs, one of less then 30 MB and one of about 40 GB. I noticed right away the system became very unresponsive. I looked at the processes cpu usage and did not see anything very high so I tried to do some other stuff my system and it locked up and I had to force a restart. A few minutes later the system locked up again but I had a terminal open and was able to shut it down from there. This morning I started the computer up again and let it set for 10 minutes or so and then looked at it. The ownCloud process was only using 8-12 percent of the cpu and nothing else in the system monitor was using much. But when I looked at the System Load tab three cpu threads where stuck at 100 percent and the fourth was jumping between 60 and a 100 percent. So I am not sure why the discrepancy. During that time the system was really slow. It took 3 to 5 minutes to load fire fox. There was also lots of disk activity. I paused both syncs in ownCloud but that did not help, so I stopped the ownCloud process and the cpu usage dropped down to basically zero over the next few seconds.

After that I tried to restart ownCloud client but it would not come up. The icon appeared on the system try and would say in a pop up that syncing was disabled but clicking on it or ownCloud in the start menu would do nothing.

I then restarted Kubuntu and ownCloud client popped right up on the screen, both syncs were paused. I waited a minute, then started the smaller sync. Most of the cpu's hit 60-80 percent but then went right back down. I waited a few minutes and then started the large sync. It quickly jumped up to one cpu running about a 100 percent (not always the same one), but the others were low. After a minute or so two cpu's hit 100% and basically stayed there. In about an about another minute we had three cpu's at 100%. It varied a little bit after that. Some times they would all be 100% and other times only one would be 100% and the rest would be less. But for the most part they stayed maxed out. The ownCloud process itself seemed to only take about 15% most of the time according to the process monitor. The system stayed responsive for a few minutes more. At some point all network traffic dropped off, but the cpu usage stayed maxed out. The outbound network traffic eventually came back but at a fairly slow rate.

After about ten minutes of this the ram usage suddenly started climbing so I switch to the process tab and it was the ownCloud process that was using most of it. The system has four GB of ram and had been running just under one including ownCloud client. By the time ownCloud client hit three GB the system was mostly unresponsive. It made it up to 3,39x,xxx KB before even the screen would not refresh. I could not get to another console, so I had to hold the power button to force it down. When it restarted I paused the large sync.

The smaller sync of 30 MB or less seems to be working.

[guruz]

2.2.0 has a known bug with memory and possibly CPU.
2.2.1 does fix this.
Did you try a nightly build?

[FlorentCoppint]

2.2.1~nightly2016531-1.1 seems to solve the problem on Ubuntu 16.04 but CPU usage is always very high sometimes (using 100% of 1 core for a few minutes, then falls to 0%...).

[prairietree]

Where can I download the nightly builds?

[FlorentCoppint]

@prairietree http://download.opensuse.org/repositories/isv:/ownCloud:/community:/nightly/

[prairietree]

Thanks, that was fast. I downloaded owncloud-client_2.2.1~nightly2016531-1.1_amd64.deb and will give it a try and let you know what happens.

[prairietree]

Installed build Version 2.2.1nightly2016531 (build 1660), and monitored the same large sync for 30 minutes. Most of the time cpu usage is very little but ram usage has been climbing very slowly. However nothing like it was before. I will monitor the ram usage and let you know if it climbs to some unreasonable amount, but at this point it looks like it is fixed in this build.

A big thanks to who ever fixed that and all the other developers of this client.

[guruz]

Great to hear!

[simopal6]

Using 2.2.1 (compiled from git) I get 100% CPU usage while the client scans the filesystem for updates--which is also strange, by the way, since I enabled libinotify, but apparently what it does is that when it detects a file change, it starts a full directory tree scan.

[Doooooo0o]

this was fixed on the latests releases on the repos, check the 2.2.1-13