kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stanislav Kozlovski (JIRA)" <j...@apache.org>
Subject [jira] [Created] (KAFKA-7599) Trogdor - Allow configuration for not throttling Benchmark Workers and expose messages per second
Date Tue, 06 Nov 2018 14:38:00 GMT
Stanislav Kozlovski created KAFKA-7599:
------------------------------------------

             Summary: Trogdor - Allow configuration for not throttling Benchmark Workers and
expose messages per second
                 Key: KAFKA-7599
                 URL: https://issues.apache.org/jira/browse/KAFKA-7599
             Project: Kafka
          Issue Type: Improvement
            Reporter: Stanislav Kozlovski
            Assignee: Stanislav Kozlovski


In Trogdor, the ConsumeBench, ProduceBench and RoundTrip workers all take in an argument
called "targetMessagesPerSec". That argument works as an upper bound on the number of messages
that can be consumed/produced per second in that worker.

It is useful to support infinite messages per second. Currently, if the `targetMessagesPerSec`
field is not present in the request, the RoundTripWorker will raise an exception, whereas
the ConsumeBench and ProduceBench workers will work as if they had `targetMessagesPerSec=10`.

I propose we allow for unbounded `targetMessagesPerSec` if the field is not present.
Further, it would be very useful if some of these workers showed the `messagesPerSecond` they
have been producing/consuming at. 
Even now, giving the worker a `targetMessagesPerSec` does not guarantee that the worker will
reach the needed `targetMessagesPerSec`. There is no easy way of knowing how the worker performed
- you have to subtract the status fields `startedMs` and `doneMs` to get the total duration
of the task, convert to seconds and then divide that by the `maxMessages` field.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message