Comment by a2ff6eeb0 3 hours ago If that's your design constraint, couldn't you speed it up by getting rid of the WAL? 2 comments a2ff6eeb0 Reply oneshadab 2 hours ago You'd lose durability against process crashes.If your system has a reasonable tolerance for power failure (multi-az multi-cloud), this can provide much better throughput t098i3 2 hours ago Indeed, a common enough pattern for etcd is to run it backed by a RAMdisk and have multi-az availability + periodic backups + tolerance at a business level to be OK losing some recent data.
oneshadab 2 hours ago You'd lose durability against process crashes.If your system has a reasonable tolerance for power failure (multi-az multi-cloud), this can provide much better throughput t098i3 2 hours ago Indeed, a common enough pattern for etcd is to run it backed by a RAMdisk and have multi-az availability + periodic backups + tolerance at a business level to be OK losing some recent data.
t098i3 2 hours ago Indeed, a common enough pattern for etcd is to run it backed by a RAMdisk and have multi-az availability + periodic backups + tolerance at a business level to be OK losing some recent data.
You'd lose durability against process crashes.
If your system has a reasonable tolerance for power failure (multi-az multi-cloud), this can provide much better throughput
Indeed, a common enough pattern for etcd is to run it backed by a RAMdisk and have multi-az availability + periodic backups + tolerance at a business level to be OK losing some recent data.