3 ms·

I bet queries take minutes.

• koolba 3y ago
  An indexed read should be no different than on a table with on the order of 100K rows. And that’s even with good ol’ spinning rust. It’s all about logical I/O operations which, for an indexed read, would only be a handful regardless of size as it’s operating on a btree: https://en.m.wikipedia.org/wiki/B-tree https://en.m.wikipedia.org/wiki/B-tree Now creating that index from scratch might take a while though…
• brootstrap 3y ago
  have worked on 20TB+ tables before. proper schema / index / query, shit is still fast as hell when you do it right
  • mh- 3y ago
    Yep, was just sharing this experience in the comments as well. By far the most painful part is schema migrations, and that's well-solved with pt-osc or gh-osc.
    • duskwuff 3y ago
      With MySQL 8.0+, you might not even need pt-osc. A lot of schema changes can be performed online now. https://dev.mysql.com/doc/refman/8.0/en/innodb-online-ddl-operations.html https://dev.mysql.com/doc/refman/8.0/en/innodb-online-ddl-op...
      • SteveNuts 3y ago
        And still my coworkers who 20 years ago were burned by some MySQL minor issue will laugh at the mere suggestion that we could probably use MySQL. People still think it's a toy to this day and they've struggled to shake that perception.