Bounceback option to decouple writes from read bouncebacks
A means to measure network responsiveness and throughput
Brought to you by:
rjmcmahon
Menu
▾
▴
#284 Bounceback option to decouple writes from read bouncebacks
There is a request to decouple the originating of bounceback payloads from the bounceback response, i.e. burst n bouncebacks at time t and read the bounceback return times. Currently, the new bounceback wire awaits the previous read of the previous write. Decouple this aspect of the state machine.
Please use '-P n'. I think the limit of n is 128.
I think using '-P n' is far superior to what you describe. The main advantage is that the request are sent truly simultaneously, especially that most NICs support RSS. And if you don't want simultaneous requests, you can use --no-connect-sync. The other advantage is that it's already implemented.
Also, this most likely will be incompatible with "--period 0".
ok, I think it should be compatiabile with period of zero. The new implementation will start two threads on each side and the origin sender (client side) can run continuously.
With "--period 0", the sender is throttled by the replies. That's going to be tricky. That's why I suggest to use '-P n'.