News for hackers. Stuff that matters.
Re:How We Built Uber’s Highest Query per Second Service Usin... by vvanders on Tuesday March 01, 2016 @05:15PM (#11206554)
Yup, so much this.

I always have fun trotting out Radix Sort and watching fresh CS grads try to understand how a O(kN) walks over O(NlogN) by a factor of 10x+.

Re:How We Built Uber’s Highest Query per Second Service Usin... by brianwawok on Tuesday March 01, 2016 @05:21PM (#11206596)
I also have fun busting out O(N^2) and getting a death stare. Then I ask them the biggest N could possibly be and get an answer like "16"...
Re:How We Built Uber’s Highest Query per Second Service Usin... by vvanders on Tuesday March 01, 2016 @05:33PM (#11206673)
Haha yeah,

Fun bit about Radix is it really scales well if your dataset fits in memory. Last time I benched my lame Java implementation it was about 2-5x faster than the built in Arrays.sort() on native values(float, int) and 20x faster when you started putting it up against Comparable. Trended that way well up to 65k+ entries.

It gets even better if you can drop down to a proper native language that lets you prefetch.

Re:How We Built Uber’s Highest Query per Second Service Usin... by chris_overseas on Tuesday March 01, 2016 @05:29PM (#11206646)
Absolutely. But the impression I get from the article isn't that they benchmarked their solution vs R-trees or S2 and it proved quicker, rather it seems to me they didn't bother trying the other approaches at all because of their perceived complexity. I might have the wrong end of the stick because the article doesn't go into enough detail to truly know either way. If they really didn't benchmark any other algorithms then talking about the performance of the language seems somewhat moot.