Comment 28 for bug 229745

Revision history for this message
f3a97 (f3a97) wrote : Re: [Bug 229745] Re: after fix for #215728 - Committing to urlclassifier3.sqlite still causes excessive CPU usage and disk I/O (the 2nd)

Guys,
    I was having this problem early in the Hardy release cycle, but after
months of usage on multiple machines I can say that now is almost
disappeared.

To me, it would be more correct to say that the bug is resolved, than not.

As usual, great work guys.

2008/9/12 Son <email address hidden>

>
>
> --
> after fix for #215728 - Committing to urlclassifier3.sqlite still causes
> excessive CPU usage and disk I/O (the 2nd)
> https://bugs.launchpad.net/bugs/229745
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in The Mozilla Firefox Browser: Incomplete
> Status in "firefox-3.0" source package in Ubuntu: Invalid
> Status in "xulrunner-1.9" source package in Ubuntu: Triaged
> Status in firefox-3.0 in Ubuntu Hardy: Invalid
> Status in xulrunner-1.9 in Ubuntu Hardy: Won't Fix
> Status in firefox-3.0 in Ubuntu Intrepid: Invalid
> Status in xulrunner-1.9 in Ubuntu Intrepid: Won't Fix
>
> Bug description:
> Binary package hint: firefox
>
> some follow up comments from bug #215728
>
> [ https://bugs.edge.launchpad.net/ubuntu/+bug/215728/comments/118 ]:
> Yes, there is still some heavy disk I/O going on. It's no where near as
> bad as it was before the update. This patch is a HUGE
> improvement, but it still happens from time to time causing Firefox to
> become unresponsive for a few seconds.
>
>
> [ https://bugs.edge.launchpad.net/ubuntu/+bug/215728/comments/120 ]
> actually I've just measured some firefox heavy IO activity, but as Nick
> reported, it is a matter of seconds and in my case it doesn't make the whole
> system irresponsive as it was before the patch.
>
> Luckily I had disktop running, so here is the output. I can say that the
> the slowdown that I felt was probably due to the large write of 5.5MB in 5
> seconds you can see at 18:28:31 - some random IO activity I guess.
>