[
https://issues.apache.org/jira/browse/KAFKA-4752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15867853#comment-15867853
]
ASF GitHub Bot commented on KAFKA-4752:
---------------------------------------
GitHub user enothereska opened a pull request:
https://github.com/apache/kafka/pull/2551
KAFKA-4752: Fixed bandwidth calculation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/enothereska/kafka KAFKA-4752-join-bw
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2551.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2551
----
commit f743d5e21714088f663f3bc0b105f6afe882335d
Author: Eno Thereska <e...@confluent.io>
Date: 2017-02-15T13:44:34Z
Fixed byte calculation
----
> Streams Simple Benchmark MB/sec calculation is not correct for Join operations
> ------------------------------------------------------------------------------
>
> Key: KAFKA-4752
> URL: https://issues.apache.org/jira/browse/KAFKA-4752
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 0.10.3.0
> Reporter: Damian Guy
> Assignee: Eno Thereska
> Priority: Minor
> Fix For: 0.10.3.0
>
>
> When benchmarking join operations via the {{SimpleBenchmark}} we produce 2 *
> {{numRecords}}, i.e, {{numRecords}} to topic1 and {{numRecords}} to topic2.
> The {{CountDownLatch}} in the {{foreach}} keeps processing until it has
> received {{numRecords}}. As this is the {{numRecords}} produced from the
> join, the size of each record will either be {{VALUE_SIZE}} or {{2 *
> VALUE_SIZE}}. The MB/s calculation doesn't take this into account.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
