3 ms·
We're storing floats at one minute resolution . We could have thousands of writes a second at peak load . Reads are not that heavy for now .
by thewarrior 11y ago
We're storing floats at one minute resolution . We could have thousands of writes a second at peak load . Reads are not that heavy for now .
- kasey_junk 11y agoThe read volume is much less important than the kinds of queries you want to run on the data set. But from the sounds of it you do not have a SQL problem, the data doesn't have/need varying query styles/indexes, it probably degrades in importance quickly over time, and it isn't interrelated. Use one of the umpteenth time series databases that were written for this problem. That said, any decently tuned RDBMS/sql app can easily handle thousands of writes a second, especially if you are just dumping them into giant buckets of resolution.