Open Bug 1633925 Opened 4 years ago Updated 2 years ago

Defer writes to preferences database until after startup

Categories

(Core :: Preferences: Backend, enhancement)

Product:
Core
Component:
Preferences: Backend
Type:
enhancement

Tracking

()

Project Flags:
Performance Impact none

People

(Reporter: alexical, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

(Keywords: perf:startup)

I'm working my way through a profile of a cold Firefox startup taken via Procmon right now, and I noticed three WriteFiles before startup finished via PWRunnable. These are on a background thread pool, but cold startup on spinny disks is generally heavily IO bound, so regardless of where the IO happens it's a problem. Can we defer these until after startup, or is there a material risk of doing so in the event of, say, a startup crash? I feel like if we're setting a pref during startup where it's mission critical that we don't crash before we write it to disk, then that's a problem in itself.

See Also: → 1633930
Depends on: 1637024
Whiteboard: [fxperf] → [fxperf:p2]
Keywords: perf:startup
Whiteboard: [fxperf:p2]
Performance Impact: --- → ?
Performance Impact: ? → -
You need to log in before you can comment on or make changes to this bug.