Closed Bug 551845 Opened 14 years ago Closed 12 years ago

Need to investigate performance of Array.sort

Categories

(Tamarin Graveyard :: Virtual Machine, defect)

x86
All
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED WORKSFORME
Future

People

(Reporter: cpeyer, Unassigned)

References

Details

Attachments

(2 files)

2.92 KB, text/plain
Details
2.74 KB, application/x-applix-spreadsheet
Details
Spidermonkey test:

spidermonkey/js1_5/Array/regress-99120-01

checks that "sort() should not be O(N^2) on sorted data"

mac 10.5 interp; all debug/debugger builds and arm builds intermittently return 2 for the sort order.

This is a placeholder bug to investigate whether this is an actual performance issue to be worried about.  I'd assume that debug performance is to be expected, as is arm, but the fact that it happens in interp merits investigation.
Flags: in-testsuite+
Flags: flashplayer-triage+
Test has been modified to only fail with the sort order is < 3 (instead of < 2).  This should be changed back once investigation is finished.
Flags: flashplayer-qrb+
Target Milestone: --- → Future
Attached file test source
Test file since it is now removed from redux
Attached file second test
since it is testing the performance behavior of sort, consider making this into a performance test.
Assignee: cpeyer → nobody
Blocks: 645018
Should be fine in current JS engine.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
(this was technically a bug against Tamarin, an ECMAscript/Actionscript engine, not a JS engine.  but then again, since no one has looked further at this bug in over two years, it is probably fine to leave it closed.)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: