Closed Bug 578133 (JaegerSpeed) Opened 10 years ago Closed 7 years ago
[meta] JM: Make us fast!
As of 2010 Jul 12, we need to chop off about 380 ms from our SunSpider score and up our V8 numbers by an amount TBD. Bugs to produce the wins to get us there should be linked here so we know what they are and don't forget them. Expected speedups should also be given so we can see what speedup we already have pending.
Depends on: 573083
Depends on: JaegerCalls
No longer depends on: 578272
Depends on: 557378
No longer depends on: 578912
A request: as people finish these bugs, please post SunSpider comparisons, so we can check the expected win against the actual win, and make sure that we're on track to get where we need to be.
Depends on: 582152
Depends on: 592965
Depends on: 592976
10 days since the last update to arewefastyet.com (15 sep) Whats up with that? (Is there a better place to ask, please forgive my bug spam.)
(In reply to comment #2) > 10 days since the last update to arewefastyet.com (15 sep) It was updated today, maybe just while you were posting. Points on the main graphs are only updated when there's a new point of importance. For the most up to date data, use the regress-x86 view: http://www.arewefastyet.com/?machine=6 Nice little landmark with today's point: JM+TM beats Apple Nitro on v8bench
I would absolutely love having a graph for Kraken as well. Is that doable?
Trying to run Kraken on the Fennec 4 beta 1 the device (n900) freezes and locks up requiring a hard reset. Shall I file a bug?
TM+JM is the fastest on Sunspider now. Quite nice to have the big "No" gone from arewefastyet.com :)
Really, I meant that. Filter on jm-cleanup.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.