Closed
Bug 551845
Opened 15 years ago
Closed 12 years ago
Need to investigate performance of Array.sort
Categories
(Tamarin Graveyard :: Virtual Machine, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
Future
People
(Reporter: cpeyer, Unassigned)
References
Details
Attachments
(2 files)
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+
Reporter | ||
Comment 1•15 years ago
|
||
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.
Reporter | ||
Comment 2•15 years ago
|
||
Test file since it is now removed from redux
Reporter | ||
Comment 3•15 years ago
|
||
Comment 4•15 years ago
|
||
since it is testing the performance behavior of sort, consider making this into a performance test.
Reporter | ||
Updated•14 years ago
|
Assignee: cpeyer → nobody
Updated•13 years ago
|
Blocks: array-tracker
Comment 5•12 years ago
|
||
Should be fine in current JS engine.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Comment 6•12 years ago
|
||
(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.
Description
•