It depends on the context. For example, imagine telling a teenager that their face is covered in acne, or (to use an old example of pg's) telling an old person that they will die soon (https://news.ycombinator.com/item?id=6539403). It's not hard to imagine contexts in which pointing out those facts would be being a jerk.
> you don't need to start a meta-discussion thread, which is itself a discouraged practice
That's true in general. I'm a mod here (sorry if that wasn't clear) and part of my job is to post replies when people are breaking the site guidelines. You're right that such comments are off topic and tediously meta - but it's a form of out-of-band communication that is necessary for keeping the site on-kilter. If it helps at all, these comments are even more tedious to write than they are to read :)
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.
Good 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.
Durable 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.
I'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.
Please don't be a jerk or put down others' work on HN. That's not the kind of site we're trying to be.
You're welcome to make your substantive points thoughtfully, of course.
https://news.ycombinator.com/newsguidelines.html
https://news.ycombinator.com/showhn.html
Pointing out facts is not being a jerk. If you don't want feedback, don't solicit it.
Also if you disapprove, modding down is enough, you don't need to start a meta-discussion thread, which is itself a discouraged practice.
It depends on the context. For example, imagine telling a teenager that their face is covered in acne, or (to use an old example of pg's) telling an old person that they will die soon (https://news.ycombinator.com/item?id=6539403). It's not hard to imagine contexts in which pointing out those facts would be being a jerk.
There are infinitely many facts. They don't select themselves—humans do that, and we do it for reasons which are not particularly factual (https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...).
> If you don't want feedback, don't solicit it.
If you read the lower part of https://news.ycombinator.com/showhn.html you'll see that the site has specific rules around how to offer feedback.
> you don't need to start a meta-discussion thread, which is itself a discouraged practice
That's true in general. I'm a mod here (sorry if that wasn't clear) and part of my job is to post replies when people are breaking the site guidelines. You're right that such comments are off topic and tediously meta - but it's a form of out-of-band communication that is necessary for keeping the site on-kilter. If it helps at all, these comments are even more tedious to write than they are to read :)
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.
Good 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.
Durable 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.
A NVMe disk write is 20 microseconds.
I'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.
If 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.