On Wednesday, May 20, 2015 at 4:26:40 PM UTC-4, Andrei Zh wrote: > > >>> > Well, if they don't use any tricks like passing data through shared memory > or heavy batching, then it's pretty impressive. But, as you mentioned, in > this particular case Caché is not an option. >
I would say that *any* decent database does "tricks" like using shared memory... Aerospike does, I don't know about Redis... Caché has a large shared buffer pool... all processes can read or wrote B+ tree blocks via that buffer pool, and there are daemons that take care of making sure the journal is sync'ed to disk, that the blocks get out to disk every so often, etc.
