Open
Bug 831510
Opened 12 years ago
Updated 2 years ago
[meta] Fix gbemu.js performance (octane benchmark)
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
NEW
People
(Reporter: sstangl, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: meta)
gbemu.js needs a 21% speedup to match v8 performance: 10578 versus 12777 locally.
Comment 1•11 years ago
|
||
Is this fixed by now? For the online Version on my Box we're 29% faster than v8.
Comment 2•11 years ago
|
||
AWFY says SM usually gets mid 36,000s vs V8's mid 35,000s, but SM occasionally dips lower, sometimes drastically (e.g. often down to 30,000, sometimes down to 11,000). I wonder if GC is the cause of the dips.
Assignee | ||
Updated•10 years ago
|
Assignee: general → nobody
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•