Closed
Bug 549512
Opened 16 years ago
Closed 16 years ago
JM: Get V8 benchmarks working
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
People
(Reporter: dmandelin, Assigned: dmandelin)
References
Details
Attachments
(1 file, 1 obsolete file)
|
27.47 KB,
patch
|
Details | Diff | Splinter Review |
We should get all of the V8 benchmarks running in Jaeger mode so we can start seeing what perf effects we're getting there, especially since those benchmarks are harder to trace, and should thus benefit more in practice from JM.
The first two JSOps that we abort on are deflocalfun_fc and initmethod, but there are others lurking.
| Assignee | ||
Updated•16 years ago
|
Assignee: general → dmandelin
| Assignee | ||
Comment 1•16 years ago
|
||
ETA is Friday 5 Mar 2010.
I don't even know how many ops need to be added, so this is a very rough estimate.
| Assignee | ||
Comment 2•16 years ago
|
||
Almost done. I just need to update the throwpoline for x64.
| Assignee | ||
Comment 3•16 years ago
|
||
Attachment #430125 -
Attachment is obsolete: true
| Assignee | ||
Comment 4•16 years ago
|
||
Landed. I currently see a 6% speedup on the v8 benchmarks on my machine. It's a start.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 5•16 years ago
|
||
ETA was 5 Mar 2010.
Actual was 3 Mar 2010.
Main reason for the estimation error was that I didn't know how many ops I needed to do so I gave a very conservative estimate.
You need to log in
before you can comment on or make changes to this bug.
Description
•