blog.allegro.tech/2024/03/kafka-performance-analysis.html
Preview meta tags from the blog.allegro.tech website.
Linked Hostnames
14- 16 links toblog.allegro.tech
- 9 links togithub.com
- 6 links toelixir.bootlin.com
- 2 links tokafka.apache.org
- 2 links towww.brendangregg.com
- 1 link toabout.allegro.eu
- 1 link toallegro.tech
- 1 link todeveloper.confluent.io
Thumbnail

Search Engine Appearance
Unlocking Kafka’s Potential: Tackling Tail Latency with eBPF
At Allegro, we use Kafka as a backbone for asynchronous communication between microservices. With up to 300k messages published and 1M messages consumed every second, it is a key part of our infrastructure. A few months ago, in our main Kafka cluster, we noticed the following discrepancy: while median response times for produce requests were in single-digit milliseconds, the tail latency was much worse. Namely, the p99 latency was up to 1 second, and the p999 latency was up to 3 seconds. This was unacceptable for a new project that we were about to start, so we decided to look into this issue. In this blog post, we would like to describe our journey — how we used Kafka protocol sniffing and eBPF to identify and remove the performance bottleneck.
Bing
Unlocking Kafka’s Potential: Tackling Tail Latency with eBPF
At Allegro, we use Kafka as a backbone for asynchronous communication between microservices. With up to 300k messages published and 1M messages consumed every second, it is a key part of our infrastructure. A few months ago, in our main Kafka cluster, we noticed the following discrepancy: while median response times for produce requests were in single-digit milliseconds, the tail latency was much worse. Namely, the p99 latency was up to 1 second, and the p999 latency was up to 3 seconds. This was unacceptable for a new project that we were about to start, so we decided to look into this issue. In this blog post, we would like to describe our journey — how we used Kafka protocol sniffing and eBPF to identify and remove the performance bottleneck.
DuckDuckGo
Unlocking Kafka’s Potential: Tackling Tail Latency with eBPF
At Allegro, we use Kafka as a backbone for asynchronous communication between microservices. With up to 300k messages published and 1M messages consumed every second, it is a key part of our infrastructure. A few months ago, in our main Kafka cluster, we noticed the following discrepancy: while median response times for produce requests were in single-digit milliseconds, the tail latency was much worse. Namely, the p99 latency was up to 1 second, and the p999 latency was up to 3 seconds. This was unacceptable for a new project that we were about to start, so we decided to look into this issue. In this blog post, we would like to describe our journey — how we used Kafka protocol sniffing and eBPF to identify and remove the performance bottleneck.
General Meta Tags
7- titleUnlocking Kafka’s Potential: Tackling Tail Latency with eBPF | blog.allegro.tech
- charsetUTF-8
- viewportwidth=device-width, initial-scale=1.0
- generatorJekyll v4.4.1
- descriptionAt Allegro, we use Kafka as a backbone for asynchronous communication between microservices. With up to 300k messages published and 1M messages consumed every second, it is a key part of our infrastructure. A few months ago, in our main Kafka cluster, we noticed the following discrepancy: while median response times for produce requests were in single-digit milliseconds, the tail latency was much worse. Namely, the p99 latency was up to 1 second, and the p999 latency was up to 3 seconds. This was unacceptable for a new project that we were about to start, so we decided to look into this issue. In this blog post, we would like to describe our journey — how we used Kafka protocol sniffing and eBPF to identify and remove the performance bottleneck.
Open Graph Meta Tags
7- og:titleUnlocking Kafka’s Potential: Tackling Tail Latency with eBPF
og:locale
en_US- og:descriptionAt Allegro, we use Kafka as a backbone for asynchronous communication between microservices. With up to 300k messages published and 1M messages consumed every second, it is a key part of our infrastructure. A few months ago, in our main Kafka cluster, we noticed the following discrepancy: while median response times for produce requests were in single-digit milliseconds, the tail latency was much worse. Namely, the p99 latency was up to 1 second, and the p999 latency was up to 3 seconds. This was unacceptable for a new project that we were about to start, so we decided to look into this issue. In this blog post, we would like to describe our journey — how we used Kafka protocol sniffing and eBPF to identify and remove the performance bottleneck.
- og:urlhttps://blog.allegro.tech/2024/03/kafka-performance-analysis.html
- og:site_nameblog.allegro.tech
Twitter Meta Tags
1- twitter:cardsummary
Link Tags
5- alternate/feed.xml
- canonicalhttps://blog.allegro.tech/2024/03/kafka-performance-analysis.html
- icon/favicon.ico
- stylesheet/assets/css/main.css?v=
- stylesheet/assets/css/highlights.css?v=
Links
44- https://about.allegro.eu/who-we-are/at-a-glance
- https://allegro.tech
- https://blog.allegro.tech
- https://blog.allegro.tech/about
- https://blog.allegro.tech/authors