TeapotNotKettle

Maybe - but if that’s the case you are likely using the wrong data structure.

Additionally you are going to be memory starving every other thread/process because you are hogging all the memory channels, and making an already bad L3 cache situation worse.

Outside of extremely niche realtime use cases (which would generally fit in L3 cache) I can’t see how this would improve overall throughput, once you take into account other processes running on the same box.

Do you have an example use case?

Very interesting work.

But practically speaking, in a real application - isn’t any performance benefit going to be lost by the reduced cache hit rate caused by having a larger working set? Or are the reads of all-but-one of the replicas non-cached?

Apologies if I am missing something.

“Burn old fella burn”, felt like political speech - but that didn’t work out so well.

So you were wrong?

And in each of those 62 cases they gave up there and then ? Tells you something

Misconfigured clown - bad news indeed.

“ Perhaps my old age and fearfulness deceive me, but I suspect that the human species - the unique species - is about to be extinguished, but the Library will endure: illuminated, solitary, infinite, perfectly motionless, equipped with precious volumes, useless, incorruptible, secret.”