Elliot Gorokhovsky wrote: > I ran the > benchmark a couple of times and the numbers seem to exactly line up > something like one in five times; perhaps not that crazy considering > they're executing nearly the same code? Could this be a result of a time being measured in seconds somewhere and then divided down? > *** 1e7 ints + 1 float (to disable the optimization while keeping the precheck)*** > F.fastsort(): 7.57237982749939 > F.sort(): 7.666172504425049 This result looks a bit suspicious too -- it's hard to see how fastsort could be faster even when the optimisation is not being used. -- Greg
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4