4 ms·
EDIT: Thank you for clarification. It is a fair 3 node vs 3 node benchmark. Does this benchmark compare both 3 node Kafka against 3 node Redpanda cluster? It's
by globalreset 3y ago
EDIT: Thank you for clarification. It is a fair 3 node vs 3 node benchmark.
Does this benchmark compare both 3 node Kafka against 3 node Redpanda cluster? It's unclear.
- AtNightWeCode 3y agoSurely nobody runs 3 Kafka nodes in production, no?
- winrid 3y agoI know of several production clusters at 50m+ ARR companies with three nodes.
- jvanlightly 3y agoAuthor here. Yes both Kafka and Redpanda were deployed on identical hardware: three i3en.6xlarge.
- jpgvm 3y agoI'm not sure which of us read it correctly. I -think- they are saying the original benchmark results done by RedPanda show a 9 node Kafka cluster being beaten by a 3 node RP cluster. This new benchmark I assume is being done on identical hardware (i.e 3 nodes for both) just with less terrible Kafka settings.
- globalreset 3y agoI'm confused because it's never clarified, and it starts with: > According to their Redpanda vs Kafka benchmark and their Total Cost of Ownership analysis, if you have a 1 GB/s workload, you only need three i3en.6xlarge instances with Redpanda, whereas Apache Kafka needs nine and still has poor performance. but scanning it again, I think they are in fact doing 3 node vs 3 node benchmark. It's just a bit unclear.
- comet-engine 3y agoI had to go to the repo to see the benchmarking setup to get an answer. Looks like 3 Kafka nodes. https://github.com/Vanlightly/openmessaging-benchmark-custom/tree/main/driver-kafka https://github.com/Vanlightly/openmessaging-benchmark-custom...