In this case producer.send() should not be blocking since it does not check
on the returned future (i.e. not waiting on the ack).
On Wed, Jul 15, 2015 at 12:57 PM, Yuheng Du
wrote:
> Thanks. Here is the source code snippet of EndtoEndLatency test:
>
>
> for (i<- 0 until numMessages) { val begin
Thanks. Here is the source code snippet of EndtoEndLatency test:
for (i<- 0 until numMessages) { val begin = System.nanoTime producer.send(
new ProducerRecord[Array[Byte],Array[Byte]](topic, message)) val received =
iter.next val elapsed = System.nanoTime - begin // poor man's progress bar
if (i
The end-to-end latency record the transferring of a message from producer
to broker, then to consumer.
I cannot remember the details not but I think the EndtoEndLatency test
record the latency as average, hence it is small.
Guozhang
On Wed, Jul 15, 2015 at 12:28 PM, Yuheng Du
wrote:
> Guozhang
Guozhang,
Thank you for explaining. I see that in ProducerPerformance call back
functions were used to get the latency metrics.
For the TestEndtoEndLatency, does message size matter? What this end-to-end
latency comprise of, besides transferring a package from source to
destination (typically arou
Yuheng,
Only TestEndtoEndLatency's number are end to end, for ProducerPerformance
the latency is for the send-to-ack latency, which increases as batch size
increases.
Guozhang
On Wed, Jul 15, 2015 at 11:36 AM, Yuheng Du
wrote:
> In kafka performance tests https://gist.github.com/jkreps
> /c7dd
In kafka performance tests https://gist.github.com/jkreps
/c7ddb4041ef62a900e6c
The TestEndtoEndLatency results are typically around 2ms, while the
ProducerPerformance normally has "average latency"around several hundres ms
when using batch size 8196.
Are both results talking about end to end lat
