Open Issues Need Help
View All on GitHub perf(consumer): EstimatePendingFetchBytes boxes an interface enumerator twice per partition-fetch 3 days ago
good first issue performance P3 consumer in-progress
good first issue performance P3 protocol in-progress
bug good first issue P3 in-progress
bug good first issue P3 consumer in-progress
bug good first issue P3 in-progress
enhancement good first issue P2 producer kafka-4.1 in-progress
bug good first issue in-progress
good first issue performance P2 in-progress
AI Summary: The `BatchArena.ReturnToPool` method unnecessarily clears large byte arrays (1MB+) when returning them to the shared `ArrayPool`, consuming 0.10% exclusive CPU. This clearing is redundant because the data is not sensitive and the buffer will be fully overwritten on its next use. The proposed fix is a one-line change to disable array clearing.
Complexity:
1/5
good first issue performance P3
Clarify consumer thread-safety documentation 5 months ago
documentation good first issue P3
bug good first issue P3
enhancement good first issue api P3
bug good first issue P1
Add Brotli compression codec 5 months ago
enhancement help wanted P3
enhancement help wanted
AI Summary: The `SendSaslMessageAsync` method in `KafkaConnection.cs` allocates three `byte[]` arrays during SASL message exchanges, which occur only during connection authentication. To reduce these avoidable memory allocations, the issue proposes using `ArrayPool<byte>` to rent and return temporary buffers.
Complexity:
2/5
enhancement good first issue
enhancement good first issue