Closed
Bug 1264305
Opened 9 years ago
Closed 7 years ago
Figure out a good benchmark for the job scheduler
Categories
(Core :: Graphics, defect, P3)
Core
Graphics
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: nical, Unassigned)
References
Details
(Whiteboard: [gfx-noted])
So far I have experimented with either very small jobs (a bit too micro-benchmark-ish to my taste) or big painting jobs with the multithreaded DrawTarget. The latter needs all of gecko which isn't an ideal workflow.
I'd like to settle for a set of more representative jobs to test from something simple like gtest, and that would be usefull for more than the DrawTarget usecase.
Whiteboard: [gfx-noted]
Comment 1•9 years ago
|
||
There's a setup for GTest benchmark BTW. You might want to take a look at that for microbenchmark. Not bad to block un-intended regressions.
Updated•7 years ago
|
Priority: -- → P3
Reporter | ||
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•