Wait for response option?

[foobarna]

Hi,
First of all, great utility you've written here!

I try to understand it and test a TCP protocol that I wrote. I run it with this command
tcpkali --unescape-message-args --latency-connect --latency-marker '\x00\x01' --latency-percentiles 50,100 -r 10 -c 1000 -T20s -1 '\x35\x36' -m '\x00\x01\x00\x00\x7C\x5E' <ip>:<port>
and I have this outcome

Decrease --connections=1000, or increase --duration=20 or --connect-rate=100.
Ramped up to 1000 connections.
Total data sent: 9.2 MiB (9614129 bytes)
Total data received: 198.2 KiB (203003 bytes)
Bandwidth per channel: 0.004⇅ Mbps (0.5 kBps)
Aggregate bandwidth: 0.081↓, 3.843↑ Mbps
Packet rate estimate: 36.7↓, 10009.1↑ (1↓, 1↑ TCP MSS/op)
TCP connect latency at percentiles: 0.1/495.1 ms (50/100%)
Message latency at percentiles: 1391.1/12428.7 ms (50/100%)
Test duration: 20.0112 s.

From what I understand is this: tcpkali sent out ~10k packets per second and only received ~36 per second. And the rest, can't really understand.

Also, is there an option to say something like "don't send the next request until the server sent back something" ?
By having this option, we can actually test a protocol.

[mochetts]

I have the same doubt. Did anyone find a solution? Thanks!