Closed Bug 1088293 Opened 11 years ago Closed 2 years ago

Dromaeo Object String is a lot slower with PGO

Categories

(Core :: JavaScript Engine: JIT, defect, P5)

x86_64
Windows 7
defect

Tracking

()

RESOLVED WONTFIX

People

(Reporter: guijoselito, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: perf)

According to http://arewefastyet.com/#machine=17&view=single&suite=dromaeo&subtest=dromaeo-object-string Nightly with PGO is 60% slower than without. The last 2 patches from bug 1074961 cut 1/3 from the distance (but were backed out). All the other tests from Dromaeo perform better or at the same level with PGO.
Flags: needinfo?(jdemooij)
I don't know how, but something in this range improved a lot the PGO version: http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=19beeeec9cf3&tochange=927503f08f55 PGO is now only ~5% slower than without.
AWFY shows this is bimodal now: http://arewefastyet.com/#machine=17&view=single&suite=dromaeo&subtest=dromaeo-object-string Some runs are fast, others are slow... The non-PGO build doesn't have this issue; might be a timing/GC thing in the profile run? :( I'll clear the needinfo; it's not super urgent and I'm drowning in needinfo/review requests atm.
Flags: needinfo?(jdemooij)
Keywords: perf
I checked AWFY again and this is still bimodal, with PGO builds sometimes ~50% slower.
Blocks: sm-js-perf
Priority: -- → P5
Severity: normal → S3

PGO has been the default for a long time, and Dromaeo is no longer the most relavent benchmark. Closing this.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.