Closed
Bug 683629
Opened 14 years ago
Closed 4 years ago
TI: performance regression on the Dromaeo eval tests
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: bzbarsky, Assigned: bhackett1024)
References
()
Details
(Keywords: regression, Whiteboard: js-triage-needed)
http://dromaeo.com/?id=148654,148653 is pre-TI-landing vs post-TI-with-closure-fix. The |new Function| thing got a bit slower; eval() got 2x slower.
It's not clear why this is happening, esp. for eval().
|
Reporter | |
Updated•14 years ago
|
Keywords: regression
|
||
Comment 1•14 years ago
|
||
We need to get this triaged at the very least.
Assignee: general → bhackett1024
Whiteboard: js-triage-needed
|
|
||
Comment 2•12 years ago
|
||
After 2 years, and the engine changes, this bug shouldn't be about the regression anymore (I guess).
Comparing the results with Chrome, Firefox is 4,44x faster on "Normal eval".
But on "new Function" Chrome is 4,1x faster.
http://dromaeo.com/?id=203814,203815
The problem is https://bugzilla.mozilla.org/show_bug.cgi?id=579234 ?
|
||
Updated•4 years ago
|
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•