Open
Bug 561486
Opened 15 years ago
Updated 2 years ago
GC benchmark automation
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
NEW
People
(Reporter: jorendorff, Unassigned)
References
(Blocks 1 open bug)
Details
It should be possible to measure GC performance in ordinary release builds.
It should happen automatically, and we should track the numbers over time, the way we do for other JS benchmarks.
Comment 1•15 years ago
|
||
| Reporter | ||
Comment 2•15 years ago
|
||
On IRC, ctalbert wrote (lightly edited): In general all the Talos tests are extensions that register a command line handler with firefox. Firefox is launched using that command, the extension does what it needs to do and reports numbers to stdout or an html page.
So we can reuse one of the existing extensions (Tsunspider reuses the pageload chrome) or write our own little extension (taras and jmaher did this for Fennec).
| Reporter | ||
Updated•15 years ago
|
Assignee: general → jorendorff
Comment 3•3 years ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months.
:sdetar, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee: jorendorff → nobody
Flags: needinfo?(sdetar)
Updated•3 years ago
|
Flags: needinfo?(sdetar)
Updated•3 years ago
|
Severity: normal → S3
Updated•2 years ago
|
Blocks: GC.performance
You need to log in
before you can comment on or make changes to this bug.
Description
•