3 ms·
And nobody does reads at quorum, they're slow. People do reads at closest, even when they really need quorum.
by GauntletWizard 4y ago
And nobody does reads at quorum, they're slow. People do reads at closest, even when they really need quorum.
- mping 4y agoUnless they want "read your writes", otherwise bugs start appearing "why isn't the data i just put showing"?
- deleted 4y ago[deleted]
- YZF 4y agoI don't think that's true. Can't speak for everybody but for the stuff I worked on. Quorum reads at RF=3 are only twice as slow as reading a single node and it's pretty practical, if you care about it, to write and read using quorum writes/reads. It's true there's many applications where you're ok with some time not reading your latest data, and for those you can get somewhere better performance/latency for a given scale by going CL=ONE...