5 ms·
Totally fair, if this were “single-node HTTP handler on localhost”, then yeah, you can hit big numbers quickly in many stacks. The point of these numbers is th
by Aydarbek 8mo ago
Totally fair, if this were “single-node HTTP handler on localhost”, then yeah, you can hit big numbers quickly in many stacks.
The point of these numbers is the envelope: 3-node consensus (Raft), real network (not loopback), and sync-majority writes (ACK after 2/3 replicas) plus the crash/recovery semantics (SIGKILL → restart → offsets/data still there).
If you have a quick Python setup that does majority-acked replication + fast crash recovery with similar measurements, I’d honestly love to compare apples-to-apples happy to share exact scripts/config and run the same test conditions.
- mgaunard 8mo agoGood NICs get data out in a microsecond or two. That's still off by quite the order of magnitude, but that could be up to the network topology in question.
- hedgehog 8mo agoDurable consensus means this is waiting for confirmed write to disk on a majority of nodes, it will always be much slower than the time it takes a NIC to put bits on the wire. That's the price of durability until someone figures out a more efficient way.
- mgaunard 8mo agoA NVMe disk write is 20 microseconds.
- hedgehog 8mo agoI'm not sure if you're going out of your way to be a dick or just obtuse but 1) that's not true on most SSDs, 2) there's overhead with all the indirection on a Digital Ocean droplet, and 3) this is obviously a straight forward user space implementation that's going to have all kinds of scheduler overhead. I'm not sure who it's for but it seems to make some reasonable trades for simplicity.
- mgaunard 8mo agoIf it's about making trade-offs for simplicity then use Kafka. Some poor quality software with bad performance, but an established piece of tech regardless.