[
https://issues.apache.org/jira/browse/KAFKA-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13140368#comment-13140368
]
Jun Rao commented on KAFKA-175:
-------------------------------
A few comments:
1. Testing on batch size is a bit confusing since how big a batch is really
depends on message size. What really matters is the size of each
ProduceRequest. So, maybe we should choose the request size as the variable
instead.
2. Can we merge producer-throughput-over-batch-size.sh and
zk-producer-throughput-over-batch-size.sh into a single script and add an
option to allow the caller to choose either broker list or zk connect?
3. Not sure how producer-throughput-over-data-accumulated.sh is different from
producer-throughput-over-batch-size.sh. They both seem to vary batch sizes.
> Add helper scripts to wrap the current perf tools
> -------------------------------------------------
>
> Key: KAFKA-175
> URL: https://issues.apache.org/jira/browse/KAFKA-175
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Neha Narkhede
> Assignee: Neha Narkhede
> Fix For: 0.8
>
> Attachments: kafka-175.patch
>
>
> We have 3 useful tools to run producer and consumer perf tests -
> ProducerPerformance.scala, SimpleConsumerPerformance.scala and
> ConsumerPerformance.scala.
> These tests expose several options that allows you to define the load for
> each perf run. It will be good to expose some helper scripts that will cover
> some single node perf testing scenarios.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
