Open
Bug 1631954
Opened 4 years ago
Updated 2 years ago
Don't prefetch the first N bytes of omnijars if startup cache is present and valid
Categories
(Toolkit :: Startup and Profile System, enhancement)
Toolkit
Startup and Profile System
Tracking
()
ASSIGNED
Performance Impact | none |
People
(Reporter: emmamalysz, Assigned: alexical)
References
(Blocks 1 open bug)
Details
(Keywords: perf:startup)
We currently prefetch omni.ja, but this is not performant for subsequent startups that have a startup cache.
If the startup cache is present and valid, we should consider not prefetching the start of omni.ja.
Assignee | ||
Updated•4 years ago
|
Summary: Determine impact of prefetching of omni.ja → Don't prefetch the first N bytes of omnijars if startup cache is present and valid
Whiteboard: [fxperf] → [fxperf:p2]
Assignee | ||
Comment 1•4 years ago
|
||
Assignee | ||
Updated•4 years ago
|
Assignee: nobody → dothayer
Status: NEW → ASSIGNED
Updated•2 years ago
|
Keywords: perf:startup
Updated•2 years ago
|
Performance Impact: --- → ?
Updated•2 years ago
|
Whiteboard: [fxperf:p2]
Updated•2 years ago
|
Performance Impact: ? → -
You need to log in
before you can comment on or make changes to this bug.
Description
•