Open
Bug 806646
Opened 8 years ago
Updated 1 year ago
IonMonkey: Fix v8-regexp performance
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
NEW
People
(Reporter: dvander, Unassigned)
References
(Depends on 4 open bugs, Blocks 1 open bug)
Details
(Whiteboard: [ion:p1])
Our score on v8-regexp is about 1300, to Crankshaft and JSC's 3650. A 180% improvement would increase our overall v8 score by ~13-14%. This depends on bug 740015 (updating Yarr again), but that alone doesn't change our score. Newer versions of Yarr have a special JIT mode that can match without capturing subexpressions, and we'll need to use that for applicable regex functions.
![]() |
Reporter | |
Updated•8 years ago
|
Whiteboard: [ion:p1]
Comment 1•7 years ago
|
||
Seems like a not-so-nice 50% regression during mid-november (possibly due to octane upgrade) put us back close to where we started a year ago.
Comment 2•7 years ago
|
||
Yes, octane-regexp changed to require creation of the results array. Our previous optimization, MatchOnly mode, therefore no longer applies.
Comment 3•7 years ago
|
||
AWFY says that Chrome x86 is 40% faster on Win8 than OSX while Firefox stays about the same. I wonder what trick they use to do that?
Assignee | ||
Updated•7 years ago
|
Assignee: general → nobody
Comment 4•1 year ago
|
||
Perhaps the keywords "meta" and/or "tracking" should be added to this bug.
You need to log in
before you can comment on or make changes to this bug.
Description
•