![]() The remaining jank I occasionally see (~500ms) seems to come fromĪ) something related to cookie-/session-store. * getting some extensions that use to use the sameZoneAs argument which may have had an impact on the pauses caused by js::NukeCrossCompartmentWrappers bug 816784, need to take new measurements to confirm * most recently the fix for bug 1214961 helped Since reporting this bug excessive pauses (not just GC ones) have gone down a lot. We seem to call the entire list at the start of each slice, so I'd guess that this work is largely duplicated. The callFinalizeCallbacks appears to be going to - it sets two bools, so is probably not implicated. Gcstats::AutoPhase ap(stats, gcstats::PHASE_FINALIZE_START) ĬallFinalizeCallbacks(&fop, JSFINALIZE_GROUP_START) ![]() The code segment that's getting flagged is: Then, right near the end we do an extremely long GC - ~4s of GC work done over a 15s period in ~100 slices.Īt a first glance we appear to be suffering from the same symptom as I've seen elswhere recently where we're spending a ton of time in Finalize Start Callback and not getting much actual work done on each slice. There is a non-incremental GC because we've gone too long since GCing that takes only 0.5 sec or so. The majority of the GC's reported are very short DOM_WORKER GC's which we can ignore. Details Here are MOZ_GCTIMER logs from a startup with that profile with IGC. Note: On my real profile the discrepancy in startup time is even larger and more erratic, possibly due larger session store or addons interacting with the session restore Measured time (3 samples): 47s 50s 50smeasure Measured time (3 samples): 2m58s 2m57s 2m59s Used measurement method: manual tracking of CPU time (not wall time) until the initial tab from the session restore becomes scrollable after startup start profile either with incremental+compacting GC enabled or disabled load attached sessionstore into profile (should have 1 foreground tab + 1000 background tabs in a separate panorama group)ĥ. Details While the bug itself concerns pause times during regular browsing after process startup I found that compacting GC also has an impact on startup time, which is easier to compare than intermittent GCsĢ.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |