You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jiangjie Qin (JIRA)" <ji...@apache.org> on 2016/05/17 16:39:12 UTC

[jira] [Assigned] (KAFKA-3554) Generate actual data with specific compression ratio and add multi-thread support in the ProducerPerformance tool.

     [ https://issues.apache.org/jira/browse/KAFKA-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jiangjie Qin reassigned KAFKA-3554:
-----------------------------------

    Assignee: Jiangjie Qin  (was: Dong Lin)

> Generate actual data with specific compression ratio and add multi-thread support in the ProducerPerformance tool.
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-3554
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3554
>             Project: Kafka
>          Issue Type: Improvement
>    Affects Versions: 0.9.0.1
>            Reporter: Jiangjie Qin
>            Assignee: Jiangjie Qin
>             Fix For: 0.10.1.0
>
>
> Currently the ProducerPerformance always generate the payload with same bytes. This does not quite well to test the compressed data because the payload is extremely compressible no matter how big the payload is.
> We can make some changes to make it more useful for compressed messages. Currently I am generating the payload containing integer from a given range. By adjusting the range of the integers, we can get different compression ratios. 
> API wise, we can either let user to specify the integer range or the expected compression ratio (we will do some probing to get the corresponding range for the users)
> Besides that, in many cases, it is useful to have multiple producer threads when the producer threads themselves are bottleneck. Admittedly people can run multiple ProducerPerformance to achieve similar result, but it is still different from the real case when people actually use the producer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)