Investigate possible ~13% regression on sessionrestore Talos test on win32 shippable with Fission enabled
Categories
(Firefox :: Session Restore, task)
Tracking
()
People
(Reporter: mconley, Assigned: alexical)
References
Details
Assignee | ||
Updated•5 years ago
|
Reporter | ||
Comment 1•5 years ago
|
||
Hey dthayer,
I was looking at bug 1588165 the other day, and I think what I found might be related to this. It's not the same issue (the remoteness flipping not being reported for SSTabRestored), but I suspect it's that we're doing remoteness flipping where we weren't before, which is causing the parent process to do more work, which is eating up the 13%.
Anyhow, that was mainly speculation, but it might be worth looking at.
Assignee | ||
Comment 2•5 years ago
|
||
(In reply to Mike Conley (:mconley) (:⚙️) (Wayyyy behind on needinfos) from comment #1)
Hey dthayer,
I was looking at bug 1588165 the other day, and I think what I found might be related to this. It's not the same issue (the remoteness flipping not being reported for SSTabRestored), but I suspect it's that we're doing remoteness flipping where we weren't before, which is causing the parent process to do more work, which is eating up the 13%.
Anyhow, that was mainly speculation, but it might be worth looking at.
I don't see any indication of a remoteness flip? No calls to updateBrowserRemoteness or anything - for the sessionrestore test these are all lazy browsers anyway, so they shouldn't be backed by an actual process to begin with.
Assignee | ||
Comment 3•5 years ago
|
||
The delta here seems to have gone away. This is a comparison from a more recent build:
Going to close it out for now.
Description
•