Open
Bug 1807007
Opened 1 year ago
Updated 3 months ago
Timestamps for telemetry code show up in the performance profiles when running speedometer
Categories
(Core :: JavaScript Engine, task, P3)
Core
JavaScript Engine
Tracking
()
NEW
People
(Reporter: smaug, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [sp3])
https://searchfox.org/mozilla-central/rev/e6b709df9b93858364f02ab89f40d78762693db8/js/src/vm/Time.h#168
https://searchfox.org/mozilla-central/rev/e6b709df9b93858364f02ab89f40d78762693db8/js/src/jit/AutoWritableJitCode.h#55
Could we somehow avoid getting the timestamps all the time?
|
||
Comment 1•1 year ago
|
||
Are you just observing the timestamp acquisition code, or is it taking measurable time in profiles?
Also, is there a particular platform you're seeing this on?
Severity: -- → S4
Priority: -- → P3
|
Reporter | |
Comment 2•1 year ago
•
|
||
TimeStamp::Now() is slow especially on linux.
|
||
Updated•1 year ago
|
Whiteboard: [sp3]
|
||
Updated•1 year ago
|
See Also: → https://mozilla-hub.atlassian.net/browse/SP3-48
|
||
Comment 3•3 months ago
|
||
The AutoWritableJitCode one was fixed by Jamie in bug 1843534 (if JIT code write protection is disabled).
js::AutoIncrementalTimer is still being used for telemetry for baseline compilation, bytecode emission etc.
Depends on: 1843534
You need to log in
before you can comment on or make changes to this bug.
Description
•