kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chen He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-3554) Generate actual data with specific compression ratio and add multi-thread support in the ProducerPerformance tool.
Date Thu, 09 Nov 2017 06:26:00 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245266#comment-16245266
] 

Chen He commented on KAFKA-3554:
--------------------------------

This is a great feature, [~becket_qin]. What can I do for you to make it checked in to Kafka.
I am happy to contribute my time and efforts. 

> 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: 1.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.4.14#64029)

Mime
View raw message