Profiling on a JS demo increases the runtime by 50%
Categories
(Core :: Gecko Profiler, enhancement, P3)
Tracking
()
People
(Reporter: mayankleoboy1, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
42.18 KB,
text/plain
|
Details |
Enable the profiler (I use the "Gfx preset + domworkers + Task controller" , but the default "Nightly" preset is sufficient to repro)
Go to https://www.fxhash.xyz/generative/19682
Click on Open
Without profiler: 28s
With profiler: 42s https://share.firefox.dev/3GLEs56
50% overhead seems a little excessive
|
Reporter | |
Comment 1•1 year ago
|
||
|
|
Reporter | |
Comment 2•1 year ago
|
||
Enabling "No marker stacks" did not improve this.
I couldn't test it on Windows yet but I feel like this might be related to timer resolution change on Windows when we start the profiler. Could you try to check the "No Timer Resolution Change" feature in about:profiling and see if it makes any difference?
|
|
Reporter | |
Comment 4•1 year ago
|
||
(In reply to Nazım Can Altınova [:canova][:canaltinova on phabricator] from comment #3)
I couldn't test it on Windows yet but I feel like this might be related to timer resolution change on Windows when we start the profiler. Could you try to check the "No Timer Resolution Change" feature in about:profiling and see if it makes any difference?
Enabling/Disabling that option didnt make much of a difference.
Without profiler: 25s
No Timer Resolution Change Enabled :https://share.firefox.dev/3NQKR2U (37s)
No Timer Resolution Change Disabled: https://share.firefox.dev/3S6FTkU (40s)
Description
•