| Summary: | REGRESSION: These sorting idioms used by Peacekeeper and Browsermark are ~20X slower | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Geoffrey Garen <ggaren> | ||||||||||||
| Component: | New Bugs | Assignee: | Geoffrey Garen <ggaren> | ||||||||||||
| Status: | RESOLVED FIXED | ||||||||||||||
| Severity: | Normal | CC: | benjamin, fpizlo | ||||||||||||
| Priority: | P2 | ||||||||||||||
| Version: | 528+ (Nightly build) | ||||||||||||||
| Hardware: | Unspecified | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
Geoffrey Garen
2015-05-27 11:33:19 PDT
Created attachment 253797 [details]
Patch
This is a partial fix for the regression. (I'm still waiting on a build to get performance numbers.) Comment on attachment 253797 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=253797&action=review > Source/JavaScriptCore/ChangeLog:10 > + Use @toString instead of the String constructor because calls to the > + String constructor are never optimized. (See > + https://bugs.webkit.org/show_bug.cgi?id=144458.) What’s the downside of using @toString? Would we want to change this back some day if resolved bug 144458? There's no downside to @toString. Assuming that ES6 settles on making ToString and String identical in behavior, we might eventually remove @toString once @String is fast. Committed r184917: <http://trac.webkit.org/changeset/184917> Reopening to attach new patch. Created attachment 253806 [details]
Patch
Created attachment 253811 [details]
Patch
Committed r184926: <http://trac.webkit.org/changeset/184926> Reopening to attach new patch. Created attachment 253940 [details]
Patch
Created attachment 253941 [details]
Patch
Committed r185067: <http://trac.webkit.org/changeset/185067> |