News for hackers. Stuff that matters.
Re:Why Uber Engineering Switched from Postgres to MySQL by gkop on Tuesday July 26, 2016 @02:25PM (#12167723)
Illniyar is right, a b-tree with a branching factor of 100 can index 100M rows in 4 levels. Even with the index on a spinning disk, should have no trouble coming in well under 100ms.
Re:Why Uber Engineering Switched from Postgres to MySQL by falcolas on Tuesday July 26, 2016 @03:57PM (#12168335)
Indexes like this are also typically in memory to begin with, making it even faster, since you only have to find the actual record on disk.

Even better, if you only need one field from the record, and it's part of a compound index, you can frequently return the data from just the indexes; no disk seeks required. Small tip with InnoDB on MySQL - any non-primary key index is automatically a compound index with the primary key.