Bug 495957

Summary: RFE: make firefox do regular VACUUM of sqlite databases
Product: [Fedora] Fedora Reporter: Matěj Šusta <msusta>
Component: firefoxAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: bugzilla, gecko-bugs-nobody, ma, mcepl, msusta, walters
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-04-17 23:20:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Matěj Šusta 2009-04-15 17:47:49 UTC 
Description of problem:
Firefox 3 is storing lots of profile data in sqlite databases - that's fine.
But after some time, sqlite database need VACUUM command, to optimize the database, without it, Firefox performance will slowly decrease.

Steps to Reproduce:
1. install firefox
2. use firefox long-enough / intensively enough
3. see how long it takes to start it, how's the performance of address bar
  
Actual results:
Firefox on my Thinkpad T43 was starting about 30 sec., address bar was almost unusable.

Expected results:
After VACUUM of all databases, Firefox starts under 5 sec. and address bar is updating almost realtime as i type.
=> only small amount of people know about this issue and have set their cron/whatever to do this cleanup.
It'll be nice to find way, how to do this automatically.
Comment 1 Matěj Cepl 2009-04-17 23:20:39 UTC 
There is huge number of upstream bugs on this theme (I choose https://bugzilla.mozilla.org/show_bug.cgi?id=395020 to be the best one for this bug to be closed against) and believe that it is more appropriate to let it be resolved upstream.

Red Hat will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates.

Thank you for the bug report.
Comment 2 Martin Jürgens 2009-05-13 21:57:06 UTC 
*** Bug 500744 has been marked as a duplicate of this bug. ***