Earlier quoted context omitted.
> How do you figure that? RocksDB is not a programming language. I'm comparing to the code you showed. You're using the file system to dump static rows of data. All your data munging is on memory-sized blocks at program-level. Key-value stores are the comparable database for that. > You're mistaken. This is no problem in q. All of the data is mmap'd as soon as I access it (if it isn't mmap'd already). Yes, because yo…
> You're using the file system to dump static rows of data That's what MySQL, PostgreSQL, SQL Server, and Oracle all do. They write to a logfile (called the "write ahead log") then periodically (and concurrently) process it into working sets that are checkpointed (checked) in much the same way. It's a lot slower because they don't know what is actually important in the statement except what they can deduce from analy…
I don't think you are doing your case any favors with such rhetoric.