143 reputation
25
bio website
location
age
visits member for 4 years, 4 months
seen Nov 8 '10 at 17:16

Feb
4
awarded  Notable Question
Dec
19
awarded  Good Question
Oct
6
awarded  Popular Question
Aug
12
awarded  Scholar
Aug
12
accepted Mysql: Working With 192 Trillion Records… (Yes, 192 Trillion)
Aug
11
comment Mysql: Working With 192 Trillion Records… (Yes, 192 Trillion)
Sounds interesting, although I could live with false negatives - but not the false positives :)
Aug
11
awarded  Nice Question
Aug
11
awarded  Editor
Aug
11
revised Mysql: Working With 192 Trillion Records… (Yes, 192 Trillion)
added 594 characters in body; added 142 characters in body
Aug
11
comment Mysql: Working With 192 Trillion Records… (Yes, 192 Trillion)
Also backblaze does look interesting...
Aug
11
comment Mysql: Working With 192 Trillion Records… (Yes, 192 Trillion)
@ConcernedOfTunbridgeWells - to answer you questions... I need about 500 queries to return in under a second, if possible. I'll be doing this only a few hundred times a day. When a query runs though, the full table does need to be scanned. Also the INSERT's are a lower priority than the SELECT's, so it doesn't have to be anywhere near instant. I can wait a few hours for "new" data to get into the database.
Aug
8
comment Mysql: Working With 192 Trillion Records… (Yes, 192 Trillion)
Good stuff - thanks for this :)
Aug
8
comment Mysql: Working With 192 Trillion Records… (Yes, 192 Trillion)
I agree- 7PB is pretty heavy. I'd love the re-think it and find a lighter solution, but I need find find the existence (or non-existence) of a particular combination of the p fields. Splitting out the tables crossed my mind - it's more sensible, but then it just means I've got the query each table in turn. Out of interest, how many tables would you recommend splitting into here?
Aug
8
comment Mysql: Working With 192 Trillion Records… (Yes, 192 Trillion)
@andol it's 10^12
Aug
8
awarded  Student
Aug
8
comment Mysql: Working With 192 Trillion Records… (Yes, 192 Trillion)
@kaerast It's possible, yes :)
Aug
8
comment Mysql: Working With 192 Trillion Records… (Yes, 192 Trillion)
@GregD - Transactions
Aug
8
asked Mysql: Working With 192 Trillion Records… (Yes, 192 Trillion)