Closed
Bug 616441
Opened 15 years ago
Closed 15 years ago
Defragment Startup cache upon exit
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: wddn836, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b7) Gecko/20100101 Firefox/4.0b7
Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b7) Gecko/20100101 Firefox/4.0b7
By defragmenting the files in the startupcache folder and urlclassifier3.sqlite using PerfectDisk, I get a 7-second win in startup time. By defraging the files when exiting Firefox, the startup time required will be greatly reduced next time.
Reproducible: Always
Updated•15 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
| Reporter | ||
Comment 2•15 years ago
|
||
I had reviewed bug 593349 before reporting this bug. Bug 593349 aims to reduce fragmentation during the write process while my bug focus on defraging the startup cache and has nothing to do with its writing algorithms. Although they may lead to similar results (less fragments), the combined approach will make the result much more conspicious and effective. So I personally don't think it's a duplicate.
Comment 3•15 years ago
|
||
(In reply to comment #2)
> I had reviewed bug 593349 before reporting this bug. Bug 593349 aims to reduce
> fragmentation during the write process while my bug focus on defraging the
> startup cache and has nothing to do with its writing algorithms. Although they
> may lead to similar results (less fragments), the combined approach will make
> the result much more conspicious and effective. So I personally don't think
> it's a duplicate.
We can't actively defrag in firefox as that requires administrator privileges. The best we can do is try to avoid causing extra fragmentation. That said, this could be done from an addon that the user would opt in to.
Also windows is supposed to defragment periodically(once a week on hard drives).
| Reporter | ||
Updated•15 years ago
|
Resolution: DUPLICATE → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•