Closed Bug 768739 Opened 12 years ago Closed 9 years ago

IonMonkey: Fix deltablue performance

Categories

(Core :: JavaScript Engine, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: dvander, Assigned: h4writer)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

(Whiteboard: [ion:p1])

We have a large bridge to gap here (around 2X) to match Crankshaft. According to VTune our profile is: * 20% in ic-getprop-native * 17% in Plan.execute * 3% in OrderedCollection * 3% in Planner.prototype.addConstraintsConsumingTo bug 729278 should help somewhat for Plan.execute, but it looks like the bigger problem might be bug 767419. The code looks like: for (var i = 0; i < this.size(); i++) { var c = this.constraintAt(i); c.execute(); } In this situation, even if we inline through every possible |c.execute|, we'll still be left with a call to GetPropertyCache, which is unnecessary.
Summary: IonMonkey: Fix delta-blue performance → IonMonkey: Fix deltablue performance
Whiteboard: [ion:p2]
This still needs investigation, so attaching it to our V8 benchmark meta bug. According to AWFY, the current delta is roughly 6,000 points (13,000 to 19,000), which would be an increase of ~45% on our part. This would increase our V8 score by ~5%.
Blocks: 806638
No longer blocks: IonSpeed
Whiteboard: [ion:p2] → [ion:p1]
Depends on: 831268
Depends on: 837014
Depends on: 837312
Depends on: 854875
Assignee: general → hv1989
Depends on: 884298
Depends on: 884310
Depends on: 1056795
Depends on: 1059241
Depends on: 1059364
After unboxed objects landed, Firefox is the fastest on Deltablue (https://arewefastyet.com/#machine=31&view=single&suite=octane&subtest=DeltaBlue)
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.