[MASTER] Committing to urlclassifier3.sqlite causes excessive CPU usage and disk I/O
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mozilla Firefox |
Fix Released
|
Medium
|
|||
Ubuntu |
Invalid
|
Undecided
|
Unassigned | ||
Hardy |
Invalid
|
Undecided
|
Unassigned | ||
Intrepid |
Invalid
|
Undecided
|
Unassigned | ||
firefox (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Hardy |
Invalid
|
Undecided
|
Unassigned | ||
Intrepid |
Invalid
|
Undecided
|
Unassigned | ||
firefox-3.0 (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
Hardy |
Invalid
|
High
|
Unassigned | ||
Intrepid |
Invalid
|
High
|
Unassigned | ||
xulrunner-1.9 (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Hardy |
Fix Released
|
High
|
Unassigned | ||
Intrepid |
Fix Released
|
High
|
Unassigned |
Bug Description
Note: the follow up bug for this is bug #229745:
#229745 - after fix for #215728 - Committing to urlclassifier3.
===
Browsing with Firefox 3.0b5 on Hardy (All updates applied) causes Xorg to use 50-60% CPU all the time.
This is not limited to a particular site or page - it happens any time when Firefox is rendering pages.
The high CPU usage makes browsing very jerky - switching tabs takes more time than it should, pages appear frozen for a brief moment.
===
From https:/
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...
===
To reproduce:
1. enable browser.
2. observe IO on urlclassifier3.
Changed in firefox: | |
status: | Unknown → Confirmed |
Changed in firefox: | |
status: | New → Invalid |
Changed in firefox: | |
status: | Confirmed → In Progress |
Changed in firefox: | |
status: | New → Invalid |
Changed in xorg: | |
status: | New → Invalid |
Changed in xulrunner-1.9: | |
status: | New → In Progress |
importance: | Undecided → High |
status: | New → In Progress |
importance: | Undecided → High |
Changed in firefox-3.0: | |
importance: | Undecided → High |
status: | New → In Progress |
status: | Confirmed → In Progress |
importance: | Undecided → High |
Changed in xulrunner-1.9: | |
status: | In Progress → Fix Released |
Changed in firefox: | |
status: | In Progress → Fix Released |
Changed in xulrunner-1.9: | |
status: | In Progress → Fix Committed |
description: | updated |
description: | updated |
Changed in firefox-3.0: | |
status: | In Progress → Invalid |
Changed in firefox-3.0: | |
status: | In Progress → Invalid |
description: | updated |
Changed in firefox: | |
importance: | Unknown → Medium |
This is also happening here. Firefox 3 on uptodate Hardy is also causing a lot of I/O, which is probably the eventual cause of the high CPU usage. Furthermore, there is also more people affected, as evidenced in the following forum thread:
http:// ubuntuforums. org/showthread. php?t=759673