[
https://issues.apache.org/jira/browse/KAFKA-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14984276#comment-14984276
]
Dong Lin commented on KAFKA-2528:
---------------------------------
[~jkreps] Sorry for late reply. I just test the quota using latest trunk.
Please find the results below.
Configuration: The test is run with one broker, one producer performance
configured with topic=test record-size=10000 --throughput=100000, and one
console consumer which reads from topic “test” at maximum possible throughput.
Consumer always runs after producer stops. Bytes-in and bytes-out rates are
collected using one minute average after the values stabilize.
1) Unlimited quota. Broker’s bytes-in and bytes-out rates are 85 MBps and 250
MBps.
2) 1 MBps quota for both producer and consumer. Broker’s bytes-in and bytes-out
rates are 0.95 MBps and 0.98 MBps.
3) 10 MBps quota for both producer and consumer. Broker’s bytes-in and
bytes-out rates are 9.8 MBps and 9.9 MBps.
4) 50 MBps quota for both producer and consumer. Broker’s bytes-in and
bytes-out rates are 49 MBps and 49 MBps.
It appears that quota from latest trunk is working correctly now. I didn't try
to reproduce the problem in the original report, where the broker may have 2
MBps bytes-in rate in inGraph even when configured with 1 MBps produce quota.
The difference in result may possibly due to change made in Rate.java in
https://github.com/apache/kafka/pull/323.
> Quota Performance Evaluation
> ----------------------------
>
> Key: KAFKA-2528
> URL: https://issues.apache.org/jira/browse/KAFKA-2528
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Dong Lin
> Assignee: Dong Lin
> Attachments: QuotaPerformanceEvaluation.pdf
>
>
> In this document we present the results of experiments we did at LinkedIn, to
> validate the basic functionality of quota, as well as the performances
> benefits of using quota in a heterogeneous multi-tenant environment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
