Worst-case performance of quickSort / getPivot

Vladimir Panteleev vladimir at thecybershadow.net
Sat Nov 16 18:44:44 PST 2013


On Saturday, 16 November 2013 at 22:11:46 UTC, Xinok wrote:
> And the results (last number is predicate calls):
>
> Current Unstable Sort  50ms  32783474
> New Unstable Sort      69ms  21503542
> Timsort                35ms  3905887

For the record, I tried both SwapStragegy options with my data 
(the data that got me to start this thread), and although TimSort 
did fewer comparisons (predicate calls), it ran about 20% slower.


More information about the Digitalmars-d mailing list