After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 725800 - Background sync heavy load with multiple large databases
Background sync heavy load with multiple large databases
Status: RESOLVED DUPLICATE of bug 713530
Product: geary
Classification: Other
Component: ux
0.5.x
Other Mac OS
: Normal normal
: 0.6.0
Assigned To: Geary Maintainers
Geary Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-03-06 06:22 UTC by Michael Gratton
Modified: 2014-03-14 00:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Michael Gratton 2014-03-06 06:22:56 UTC 
In a similar vein as Bug 724475 (and made somewhat more pathological by the recent fix for Bug 714865), the background sync task can place a heavy load on a system when there are multiple, large accounts.

Here, with three multi-Gb account databases, when the background sync'ing is running the desktop can stutter, and system load heads north, both both CPU and I/O. There's near constant CPU fan noise!

Since it's a background task, the UX may be improved using a similar workaround as in 724475 - serialising the sync, perhaps with decreasing the reschedule interval. I guess ideally this sync process would be event driven or just made much less intensive, but that's probably a lot of work.
Comment 1 Charles Lindsay 2014-03-06 19:18:02 UTC 
We should take a look at this soon.  I'm assuming bug #714865 makes this issue worse because it made the sync happen more frequently, is that what you mean?
Comment 2 Charles Lindsay 2014-03-06 21:11:55 UTC 
Mike, can you give us a log file so we know what's going on specifically in your case?  Just the output from letting 'geary --debug' run until the problem hits and then subsides, would be great, and you can email it to us privately at geary@yorba.org (feel free to scrub it of private information first).  Thanks!
Comment 3 Jim Nelson 2014-03-14 00:26:47 UTC 
Michael, looking at your log file it's apparent that you're suffering from bug #713530, which is a bug I thought we'd eradicated but obviously have not.

I'm marking this as a duplicate and re-opening it.  (You might want to cc: yourself on that ticket.)  It may be we still need to serialize the account synchronizer, but let's fix this problem first before considering that.

*** This bug has been marked as a duplicate of bug 713530 ***
Comment 4 Michael Gratton 2014-03-14 00:29:59 UTC 
Sure thing. Bugzilla has CC'ed me already, let me know if there's anything further I can do to help.