AshenScribe opened a new pull request, #23323:
URL: https://github.com/apache/kafka/pull/23323

   removed all instances of consumer.commitSync() from EndToEndLatency.java 
(specifically inside the execute() loop and the commitAndThrow() helper method).
   
   Gradle testing:
   ./gradlew spotlessApply
   ./gradlew tools:checkstyleMain tools:checkstyleTest spotlessCheck
   ./gradlew tools:test --tests EndToEndLatencyTest
   ./gradlew tools:spotbugsMain -x test
   All succeed.
   
   Terminal 1
   ```
   KAFKA_CLUSTER_ID=$(./bin/kafka-storage.sh random-uuid)
   /bin/kafka-storage.sh format -t $KAFKA_CLUSTER_ID -c 
config/server.properties --standalone
   ./bin/kafka-server-start.sh config/server.properties
   ```
   
   Terminal 2
   ```
   ./bin/kafka-topics.sh --create --bootstrap-server localhost:9092 --topic 
latency-test-topic --partitions 1 --replication-factor 1
   ./bin/kafka-run-class.sh org.apache.kafka.tools.EndToEndLatency
   ```
   then a hard stop
   Ctrl + C
   Observed Result
   ```
   17000        0.13506
   18000        0.152582
   19000        0.142233
   20000        0.128828
   21000        0.158624
   22000        0.122607
   23000        0.10437300000000001
   24000        0.133798
   25000        0.153214
   26000        0.115744
   27000        0.166649
   28000        0.119832
   29000        0.14168199999999997
   30000        0.135822
   ```
   again
   ```
   ./bin/kafka-run-class.sh org.apache.kafka.tools.EndToEndLatency
   ```
   Observed Result
   ```
   0    36.269337
   1000 0.302741
   2000 0.268197
   3000 0.20502
   4000 0.32364
   5000 0.184502
   ```
   
   Conclusion: The latency recorded on the first loop (0 36.269337 ms) 
indicates real client connection handshakes, JIT compilation, and metadata 
initializatoin overhead.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to