The playrate are capped at ~180 TPS

[le-grimpeur]

Hey I have record a cassette with a playrate on the kafka at ~200TPS, when I replay it the playrate are caped at 180TPS even if it's configure with playback-rate at 2.0.
For information all event from the cassette are on the same partition maybe this configuration impact de rate of the replay?
If I launch multiple cassette on the same topics this time the rate increase at nb_cassette_lauch*180 TPS
When I check the CPU and GPU both are not solicit. Any idea?
Thanks you.

Edit : Even if I put the playback-rate at 0.1 the playrate on the kafka stay at 180TPS.

[fmihalic]

Hello, I am working with @le-grimpeur and I confirm that the playback-rate seems not to be taken into account when we try to use it.
We ran the same replay twice, once without playback-rate and once with playback-rate= 2.0.

You can see in the Grafana extract that the result is the same (45 transaction per second). Any idea if we are using this correctly ?

1st run
./java/java-11-openjdk-11.0.5.10-0.el7_7.x86_64/bin/java -jar kcr-all.jar --bootstrap-servers myserver:9092 play --cassette data/mytopic-20221215-133427 --topic mytopic
2nd run
./java/java-11-openjdk-11.0.5.10-0.el7_7.x86_64/bin/java -jar kcr-all.jar --bootstrap-servers myserver:9092 play --cassette data/mytopic-20221215-133427 --topic mytopic --playback-rate 2.0

[le-grimpeur]

Hey I have news of the playback-rate if it's 0, in this only case all events will be published as fast as possible as like it's supposed to be.

[dylanmei]

High playback rates could become capped due to issues with environment. But it is unexpected that values below 1.0 would show same effect!

[le-grimpeur]

Hey, In play function I don't understand why millis variable for delay is a negative value.