Way to measure processing time?

[CROprogrammer]

Hi,

is there any way to measure how long it has taken for a massage to be processed in Kafka processor using KLoadGen?

I'm thinking something like how long it took for produced message that was written to input topic, and then processed in Kafka processor, and finally written to output topic. How could I measure how long it took for specific message when it was produced, to when it was consumed?
I'm aware that KLoadGen can produce and consume messages, but can it measure time between those two action.

[jemacineiras]

Hi @CROprogrammer,

That can be a bit tricky but doable. There is a consumer sampler in Kloadgen, so the best approach here is hace producer and consumer in the test plan each one to the required topics. We populate the produced and received message into the JMeter context so here your goal is build and assertion which got the information when those messages where populated (produced and received) so you can the timestamp and obtain the difference.

We do not have an example about, so this is more or less a theoretically answer.

[CROprogrammer]

I've made Producer, Consumer, and I have Kafka Streams processor that receives messages from KLoadGen Producer, waits for 5 seconds and then writes slightly (content-wise) changed message to output topic.
When Producer produces first message, my processor works fine, and writes new message to the output topic. But the thing is that KLoadGen Consumer only consumes that message after I've run it again. I expect Consumer to wait for message to be written to the output topic from which it consumes messages rather then that I have to run KLoadGen again for it to work. Is that even possible?
And because of that I'm unable to pinpoint when message was actually consumed, and because of that processing time is unknown.

[CROprogrammer]

Is it possible for Consumer to work all the time paralley with the Producer, because my Producer works inifitely, but Consumer stops after consuming one message?

[jemacineiras]

Hi,
Consumer Sampler have a loop which waits until message is read or timeout, so it you added in the same Thread Group than the publisher you will block it. Ideally it should be run in its own Thread Group and in parallel as producer.
By default timeout is 5000 millis, I think is time moire than enough to get the message you produce in your server. I that approach does not work I will need to see your test plan file.

Cheers

[CROprogrammer]

Yeah those 5000 ms were my problem, my processor waited for 5 seconds and because of that it did not work quite right

[jemacineiras]

Timeout can be set up in the Sampler properties, under timeout.millis