News for hackers. Stuff that matters.
Re:Jepsen: Etcd 3.4.3 by gregwebs on Thursday January 30, 2020 @12:43PM (#22193397)
Etcd is designed to be able to cache it's entire working set in memory.

https://etcd.io/docs/v3.3.12/dev-guide/limit/ https://github.com/etcd-io/etcd/blob/master/Documentation/op...

TiKV, a distributed kv store that can store many terabytes of data, actually uses etcd internally for metadata storage.

Re:Jepsen: Etcd 3.4.3 by fulafel on Thursday January 30, 2020 @03:27PM (#22195167)
Most databases fit in memory though.
Re:Jepsen: Etcd 3.4.3 by aphyr on Thursday January 30, 2020 @07:32PM (#22197663)
Many do, and even large DBs can be accomodated by throwing terabytes of RAM at the problem, but etcd is fundamentally targeted at a different problem domain than a general-purpose database. Everything in etcd is represented by a single-threaded state machine, which is great for simplicity and correctness, but that comes with performance limitations.