Port over performance markers from playback to web codecs
Categories
(Core :: Audio/Video: Web Codecs, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox138 | --- | fixed |
People
(Reporter: padenot, Assigned: chunmin)
References
(Blocks 1 open bug)
Details
Attachments
(8 files, 1 obsolete file)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review |
So we can use the extension (https://github.com/padenot/fx-profiler-audio-cb) to assess web codecs's performance.
Comment 1•3 years ago
|
||
The severity field is not set for this bug.
:padenot, could you have a look please?
For more information, please visit BugBot documentation.
Updated•2 years ago
|
| Assignee | ||
Comment 2•1 year ago
|
||
| Assignee | ||
Comment 3•1 year ago
|
||
This patch introduces the "DOM Worker" thread into profiler's media
preset. Additionally, those thread names are alphabetized.
| Assignee | ||
Comment 4•1 year ago
|
||
Depends on D238713
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
| Assignee | ||
Comment 5•1 year ago
|
||
Depends on D238714
| Assignee | ||
Comment 6•1 year ago
|
||
Depends on D238879
| Assignee | ||
Comment 7•1 year ago
|
||
Depends on D238880
| Assignee | ||
Comment 8•1 year ago
|
||
Depends on D238881
Updated•1 year ago
|
| Assignee | ||
Comment 9•1 year ago
|
||
Depends on D238882
| Assignee | ||
Comment 10•1 year ago
|
||
This patch introduces a RAII-style profiler marker that automatically
starts tracking performance upon declaration and stops when
deconstructed. Additionally, it provides a manual stop method, giving
users full control over the tracking period.
Unlike passive timing based solely on the marker’s lifetime, this
approach allows developers to profile specific sections of code with
precision. This is particularly useful for accurately measuring
short-period execution, such as HW encoding or task dispatching, which
only take a few hundred or even just a few microseconds.
Depends on D239980
Comment 11•1 year ago
|
||
Comment 12•1 year ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/46606d66ed1c
https://hg.mozilla.org/mozilla-central/rev/deea9a263de6
https://hg.mozilla.org/mozilla-central/rev/38457654083f
https://hg.mozilla.org/mozilla-central/rev/8ba02172eee8
https://hg.mozilla.org/mozilla-central/rev/c0a0231ce0af
https://hg.mozilla.org/mozilla-central/rev/377f2484a381
https://hg.mozilla.org/mozilla-central/rev/9c0c76a7e749
https://hg.mozilla.org/mozilla-central/rev/ccce0bd331e0
https://hg.mozilla.org/mozilla-central/rev/db94f3c07e77
Description
•