[jira] [Updated] (KAFKA-2202) ConsumerPerformance reports a throughput much higher than the actual one
[
https://issues.apache.org/jira/browse/KAFKA-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang updated KAFKA-2202:
-
Resolution: Fixed
Fix Version/s: 0.8.3
Status: Resolved (was: Patch Available)
ConsumerPerformance reports a throughput much higher than the actual one
Key: KAFKA-2202
URL: https://issues.apache.org/jira/browse/KAFKA-2202
Project: Kafka
Issue Type: Bug
Components: tools
Affects Versions: 0.8.2.0
Reporter: Micael Capitão
Assignee: Manikumar Reddy
Priority: Minor
Fix For: 0.8.3
Attachments: KAFKA-2202.patch
I've been using the kafka.tools.ConsumerPerformance tool for some
benchmarking until in one of my tests I got a throughput much higher than the
supported by my network interface.
The test consisted in consuming around ~4900 MB from one topic using one
consumer with one thread. The reported throughput reported was ~1400 MB/s
which surpasses the 10 Gbps of the network. The time for the whole operation
was ~8 seconds, which should correspond to a throughput of ~612 MB/s.
Digging the ConsumerPerformance code, I've found this at line 73:
{code:java}
val elapsedSecs = (endMs - startMs - config.consumerConfig.consumerTimeoutMs)
/ 1000.0
{code}
The {{consumerTimeoutMs}} defined as 5000 at line 131 is always considered
leading to wrong results.
This bug seems to be related to this one
[https://issues.apache.org/jira/browse/KAFKA-1828]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KAFKA-2202) ConsumerPerformance reports a throughput much higher than the actual one
[
https://issues.apache.org/jira/browse/KAFKA-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-2202:
---
Attachment: KAFKA-2202.patch
ConsumerPerformance reports a throughput much higher than the actual one
Key: KAFKA-2202
URL: https://issues.apache.org/jira/browse/KAFKA-2202
Project: Kafka
Issue Type: Bug
Components: tools
Affects Versions: 0.8.2.0
Reporter: Micael Capitão
Priority: Minor
Attachments: KAFKA-2202.patch
I've been using the kafka.tools.ConsumerPerformance tool for some
benchmarking until in one of my tests I got a throughput much higher than the
supported by my network interface.
The test consisted in consuming around ~4900 MB from one topic using one
consumer with one thread. The reported throughput reported was ~1400 MB/s
which surpasses the 10 Gbps of the network. The time for the whole operation
was ~8 seconds, which should correspond to a throughput of ~612 MB/s.
Digging the ConsumerPerformance code, I've found this at line 73:
{code:java}
val elapsedSecs = (endMs - startMs - config.consumerConfig.consumerTimeoutMs)
/ 1000.0
{code}
The {{consumerTimeoutMs}} defined as 5000 at line 131 is always considered
leading to wrong results.
This bug seems to be related to this one
[https://issues.apache.org/jira/browse/KAFKA-1828]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KAFKA-2202) ConsumerPerformance reports a throughput much higher than the actual one
[
https://issues.apache.org/jira/browse/KAFKA-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-2202:
---
Assignee: Manikumar Reddy
Status: Patch Available (was: Open)
ConsumerPerformance reports a throughput much higher than the actual one
Key: KAFKA-2202
URL: https://issues.apache.org/jira/browse/KAFKA-2202
Project: Kafka
Issue Type: Bug
Components: tools
Affects Versions: 0.8.2.0
Reporter: Micael Capitão
Assignee: Manikumar Reddy
Priority: Minor
Attachments: KAFKA-2202.patch
I've been using the kafka.tools.ConsumerPerformance tool for some
benchmarking until in one of my tests I got a throughput much higher than the
supported by my network interface.
The test consisted in consuming around ~4900 MB from one topic using one
consumer with one thread. The reported throughput reported was ~1400 MB/s
which surpasses the 10 Gbps of the network. The time for the whole operation
was ~8 seconds, which should correspond to a throughput of ~612 MB/s.
Digging the ConsumerPerformance code, I've found this at line 73:
{code:java}
val elapsedSecs = (endMs - startMs - config.consumerConfig.consumerTimeoutMs)
/ 1000.0
{code}
The {{consumerTimeoutMs}} defined as 5000 at line 131 is always considered
leading to wrong results.
This bug seems to be related to this one
[https://issues.apache.org/jira/browse/KAFKA-1828]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
