Disclaimer: No, i’m not talking relationship advice.
When I began looking at possible database schemas for storing NetFlow data in MySQL, I was worried about space. I was working under different assumptions back then (the numbers I had for data in was 1/100th what it is now), and I was thinking that perhaps I could keep the whole database under the 32-bit boundary (for old filesystems, portability, etc.). Now that the 2GB barrier is clearly broken with the sheer amount of data I’m dealing with, I’m not concerned at all with disk space – hard drives are cheap, or so says my boss. What does this mean for the schema? No more CPU-disk tradeoffs in favor of disk space. But does that also mean I can drop additional disk space, and a bit of CPU, for coding convenience, maintainability, extensibility, and ease of use?
Continue reading ‘To Date or not to Date’
Activity
Dee Wells, Dee Wells, Maarten, Faur, Luke Murphy, Octavian Petre [...]
Freddy, Hasan, ereed, Jim, ed, Hasan [...]
Marijn Koesen, JT
WeKeBu, Budd
quipper8, Hasan, Louis, JDot