3 ms·
If your data is mutable, as in most situations where one uses a database, you still have to hit the disk for writes and wait for a disk sync before continuing a
by tomsmeding 3y ago
If your data is mutable, as in most situations where one uses a database, you still have to hit the disk for writes and wait for a disk sync before continuing after the writes.
Reads are indeed fast, but a proper RDBMS will instantly use all of that memory capacity for caching anyway, meaning that you get the same read speeds even with the RDBMS. No need to change your code.
- endisneigh 3y agoThere are certain algorithms that are more used on in memory data structures that could be leveraged and never touch disk, not just simply boosting a relational database. That being said my post was somewhat in jest