Closed Bug 410994 Opened 17 years ago Closed 10 years ago

Use Profile Guided Optimization on SpiderMonkey (all platforms)

Categories

(Core :: JavaScript Engine, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: sayrer, Unassigned)

References

Details

(Keywords: perf)

Attachments

(1 file)

I've been able to get substantial improvements with this technique using GCC. See bug 361343 for Windows data.
Attached file PGO data for Linux and Mac (deleted) —
This data shows improvements in almost all benchmarks. The exception is regex on Linux (very slight regression) and two benchmarks on Mac. I checked the Mac ones in Shark, and they both spend more than 50% of their time under JS_[Get/Set/Find]Property. That tells me these numbers are going to change substantially if we improve property access, so I'll block on a few of those bugs.
Comment on attachment 295585 [details] PGO data for Linux and Mac The Mac uses different settings than Linux because -fvpt profiling proved buggy on Darwin's gcc.
Depends on: js-propcache
Depends on: native-arrays
Keywords: perf
Version: unspecified → Trunk
Flags: wanted1.9.1?
The blocking bugs are fixed. I assume we'll give this a shot after 1.9.1?
Assignee: general → nobody
This has been done long ago. I can't find the actual bug for it, but eg bug 467271 talks about some followup fixes.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: