This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steven.daprano
Recipients alex, ezio.melotti, jtaylor, rhettinger, scoder, steven.daprano, terry.reedy, thomasahle, tim.peters, upendra-k14, vajrasky
Date 2018-05-06.10:43:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
How does the performance change with this patch?

Quick-select is a nice idea in theory, but unless it is written in C, it is unlikely to beat sorting the list unless you have HUGE data sets. Its been nearly four years since I last did some benchmarks, but at the time there was no comparison, sorting was clearly much better (although Stefan found that select was faster than sorting).

In particular, all the quickselect versions I tested suffered catastrophic performance slowdowns if the data was already sorted: anything from double the time to ten times as much time.
Date User Action Args
2018-05-06 10:43:45steven.dapranosetrecipients: + steven.daprano, tim.peters, rhettinger, terry.reedy, scoder, ezio.melotti, alex, thomasahle, jtaylor, vajrasky, upendra-k14
2018-05-06 10:43:45steven.dapranosetmessageid: <>
2018-05-06 10:43:45steven.dapranolinkissue21592 messages
2018-05-06 10:43:44steven.dapranocreate