Repository navigation
Replies: 1 comment
|
gmreads - this is the same report as your #884, which is tracked on the maintained fork as astubbs#187 with the analysis; the short version, and what has shipped since.
What v0.6.0.0 changed that touches this: the offset encoder on the commit path no longer walks every offset between the committed base and the highest succeeded one when only run-length encoding is in play (astubbs#106), and the Vert.x, Reactor and Mutiny engines got their pipeline buffer back, measured at about +10% on a dispatch-bound bench (astubbs#342) - that one does not touch the core engine you are on. Three open pull requests on the fork, none merged yet, bear on this: virtual threads for the user function (astubbs#360), and a direct-pull engine with a constant-time scan plus the benchmark harness behind it (astubbs#361, astubbs#362). Your minimal example here is what astubbs#187 lacks - a runnable reproducer. I would like to attach it there and profile it; if you can add the numbers you get on v0.6.0.0 with the two settings above, that turns the analysis into a result. The coordinates changed with the fork - on Maven Central it is now: <dependency>
<groupId>bz.stub.parallelconsumer</groupId>
<artifactId>parallel-consumer-core</artifactId>
<version>0.6.0.0</version>
</dependency>( find . -name '*.java' -exec sed -i 's/io\.confluent\.parallelconsumer/bz.stub.parallelconsumer/g' {} + |
Uh oh!
There was an error while loading. Please reload this page.
What am I doing wrong ?
Messages: 4.5 Million, with lz4 compression.
1 Topic with 1 partition
Raw Consumer -> 30-40k/sec
Parallel Consumer -> 1000/sec
Script used to find lag reduction speed
Minimal Example
Kafka consumer config
All reactions