Closed
Bug 453178
Opened 16 years ago
Closed 15 years ago
Reduce shutdown work in places
Categories
(Toolkit :: Places, defect)
Toolkit
Places
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: sdwilsh, Unassigned)
References
Details
(Keywords: meta, perf)
We do a lot of stuff that we shouldn't really be doing - let's put it in the proper place...
Updated•16 years ago
|
Target Milestone: mozilla1.9.1b1 → mozilla1.9.1
Comment 1•16 years ago
|
||
further changes will need refactoring part of expiration, so what we could do for 3.1 has been done. Other enhancements should be found for 3.2
Target Milestone: mozilla1.9.1 → ---
Comment 2•16 years ago
|
||
I was thinking ideally backup should be a fire and forget task. Actually bookmarks backup is done on 1 hour idle or on shutdown if idle did not find a good slot, and i think it takes up much time (especially for users with a lot of bookmarks). Due to the high idle time, i think vast majority of users will have to do backup on shutdown. There's no reason for backup to wait for anything, ideally it should be done in a background worker thread, without any need for idle timers, nor shutdown, the main issue is that resultNodes are not threadsafe. In the short term (3.1?) we could try reducing the idle time from 1 hour to 15 minutes, so it's less probable that the backup could happen on shutdown. This would hwv only speed up the first shutdown of every day since we have a maximum of 1 backup per day.
Comment 3•15 years ago
|
||
a bunch of work has been done here, all dependencies are fixed, new ideas will get their own bugs, but looks like we don't need this meta anymore.
You need to log in
before you can comment on or make changes to this bug.
Description
•