After looking at upstream, it looks like they have a pretty good handle on this:
"After some testing, it looks like this gets pretty bad on linux. Once we hit sqlite's cache size, sqlite starts hitting the disk pretty hard. While the database is small this isn't a big deal (we don't hit the cache limit), and once we're up-to-date it isn't as bad (we aren't adding as much data). But during the middle/end of the push to get the complete database, things take way too long, and we're thrashing the disk the whole time. We can reduce the amount of IO by increasing the cache size, and that'll help some (it'll help a whole lot if we increase the cache size by enough to hold the db). We might also need to look at throttling the update process a bit, so that we don't slam the system all at once..." -- [MASTER] High CPU Consumption https://bugs.launchpad.net/bugs/215728 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
