1559842 - (profiler-fission) [meta] [fission] Fission support in Profiler

Status: RESOLVED FIXED

(Core :: Gecko Profiler, task, P3)

Description

[Gerald Squelart (he/him) (not at Mozilla since 2022-09-15)]

The profiler uses a lot of memory per process, and one sampling thread each, which will be a challenge when Fission can potentially add hundreds of processes.

So on top of the existing tasks aiming to reduce the profiler overhead, we will probably need specific work targeted at this many-processes future.

Comment 1

[Chris Peterson [:cpeterson]]

Tentatively tracking this profiler meta bug for Fission Nightly (M6)

Comment 2

[Gerald Squelart (he/him) (not at Mozilla since 2022-09-15)]

I think we can change the Fission Milestone to "Future":

• The most important sub-task is bug 1612356 (app-global max buffer size) because it was more likely to cause crashing OOMs in Fission; and it is now fixed.
• Other tasks would help lower the profiler overhead due to having more processes, but I don't think they should block shipping Fission.
• The profiler will be used by a small number of people (moz devs, web devs, and some users from whom we've requested a profile), it is a voluntary action that is not integral to normal browser usage, so I don't think it should block shipping Fission.

But we can keep it as a "weak" dependency, to ensure that we continue making the profiler more usable in a Fission-enabled browser.

Comment 3

[Gerald Squelart (he/him) (not at Mozilla since 2022-09-15)]

I'll close this meta-bug as fixed, since the most important work has been done, and further work is probably not focused on Fission anyway.
Please reopen if you have something that would be Fission-only.