768739 - IonMonkey: Fix deltablue performance

Status: RESOLVED FIXED

(Core :: JavaScript Engine, defect)

Description

[David Anderson [:dvander] - inactive, e-mail if emergency]

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.

Comment 1

[David Anderson [:dvander] - inactive, e-mail if emergency]

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%.

Comment 2

[Guilherme Lima]

After unboxed objects landed, Firefox is the fastest on Deltablue (https://arewefastyet.com/#machine=31&view=single&suite=octane&subtest=DeltaBlue)