3 ms·
Most DB engines will use what RAM is available and even if they don't, your OS's page cache will make sure stuff is fast anyways. > What tool should I use it t
by chmod775 7y ago
Most DB engines will use what RAM is available and even if they don't, your OS's page cache will make sure stuff is fast anyways.
> What tool should I use it to load this dataset on RAM and run these queries?
The question should really be: What tool should I use to make this fast?
Postgres can be pretty fast when used correctly and you can make your data fit.
- falcolas 7y agoExactly this. DBs are really good at utilizing all the memory you give them. The query planners might give you some fits when they try and use disk tables for complicated joins, but you can work around them.
- efficax 7y agoBoth mysql and pgsql bypass the page cache if they can and maintain their own page caches. You have to do this, otherwise you’re double caching! That is, you’d have your own page cache, which you need to manage calls to read() and to know when to flush pages, while the OS would also have the same pages in its own cache. (mongodb I believe uses direct mmap access instead of a pagecache, and lmdb does this as well)