Open Bug 1928162 Opened 3 months ago Updated 3 months ago

Investigate sp3 thread contention differences between Windows and Android

Categories

(Core :: Performance Engineering, task)

Product:
Core
Component:
Performance Engineering
Type:
task

Tracking

()

People

(Reporter: mstange, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [sp3])

We see a larger gap between Firefox and Chrome performance on sp3 on Android than on Windows.
We don't have a good explanation for why this is the case.

One idea we have is that malloc lock contention may hurt us more on Android devices, see e.g. bug 1926480.

We should be able to see what percentage of the measured time the main thread is running vs not running, both on Windows and on Android, by looking at context switch markers from ETW / simpleperf.

This bug is about calculating that percentage.

With a profile that was captured with samply record --per-cpu-threads, we should be able to write some JavaScript that can be pasted on the Web Console in the Firefox Profiler, and which computes this percentage (and maybe an interruption count) by looking at the thread's CPU switch markers.

Whiteboard: [sp3]
You need to log in before you can comment on or make changes to this bug.