[
https://issues.apache.org/jira/browse/KAFKA-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739505#comment-14739505
]
Dong Lin edited comment on KAFKA-2528 at 9/10/15 8:07 PM:
----------------------------------------------------------
Yeah I think it is certainly doable, i.e. we can get very close to the target.
I can run the experiment with and without BrokerTopicMetrics.bytesInRate using
the same metric class as ClientQuotaManger.quotaSensor for calculating rate.
This should tell us whether this difference is due to metric or quota
implementation.
I did this report months ago. I recall that I tried get metric value from
ClientQuotaManger and it should be lower than 1MB for that experiment. But I
haven't written down my observation. Therefore I need to re-do the test.
was (Author: lindong):
Yeah I think it is certainly doable, i.e. we can get very close to the target.
I can run the experiment with and without BrokerTopicMetrics.bytesInRate using
the same metric class as ClientQuotaManger.quotaSensor for calculating. This
should tell us whether this difference is due to metric or quota implementation.
I did this report months ago. I recall that I tried get metric value from
ClientQuotaManger and it should be lower than 1MB for that experiment. But I
haven't written down my observation. Therefore I need to re-do the test.
> 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)
