I don't think I will ever understand why some SQL things take as long as they do
Follow
it turns out that my table of ~50 million rows had no index. So that may be part of it.
@zatnosk no, it is a pretty straight forward select:
SELECT offset, node, run, time, hears, transmitting, received FROM data WHERE run=400
and run is now an index.
It is workable, about 5 seconds per query and it returns ~200k rows.
I was just expecting it to be faster. I don't know if that was an unreasonable expectation at the start.
@inmysocks 5 seconds seems high, but I'm also not used to work with picking 200k out of 50m rows.
@inmysocks are you using any joins? Joining in the "wrong" order or using the "wrong" keys can result in multiplying two tables - which is not good if one of them has 50M rows.