You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Joe Stein (JIRA)" <ji...@apache.org> on 2013/12/23 23:03:50 UTC

[jira] [Updated] (KAFKA-1190) create a draw performance graph script

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

Joe Stein updated KAFKA-1190:
-----------------------------

    Description: 
This will be an R script to draw relevant graphs given a bunch of csv files from the above tools. The output of this script will be a bunch of png files that can be combined with some html to act as a perf report.

Here are the graphs that would be good to see:
* Latency histogram for producer
* MB/sec and messages/sec produced
* MB/sec and messages/sec consumed
* Flush time
* Errors (should not be any)
* Consumer cache hit ratio (both the bytes and count, specifically 1 
  #physical_reads / #requests and 1 - physical_bytes_read / bytes_read)
* Write merge ratio (num_physical_writes/num_produce_requests and     avg_request_size/avg_physical_write_size)
CPU, network, io, etc

  was:This will be an R script to draw relevant graphs given a bunch of csv files from the above tools. The output of this script will be a bunch of png files that can be combined with some html to act as a perf report.


> create a draw performance graph script
> --------------------------------------
>
>                 Key: KAFKA-1190
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1190
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Joe Stein
>             Fix For: 0.8.1
>
>
> This will be an R script to draw relevant graphs given a bunch of csv files from the above tools. The output of this script will be a bunch of png files that can be combined with some html to act as a perf report.
> Here are the graphs that would be good to see:
> * Latency histogram for producer
> * MB/sec and messages/sec produced
> * MB/sec and messages/sec consumed
> * Flush time
> * Errors (should not be any)
> * Consumer cache hit ratio (both the bytes and count, specifically 1 
>   #physical_reads / #requests and 1 - physical_bytes_read / bytes_read)
> * Write merge ratio (num_physical_writes/num_produce_requests and     avg_request_size/avg_physical_write_size)
> CPU, network, io, etc



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)