You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
over the last few days, I have been running some very intensive test series with Server 2019 and also 2025 to determine/compare their behaviour with a specific workload.
During the tests, for example, I also wanted to see how the systems behave with a network load with a block size of 4K with only one worker and one oIO.
Hi Friends,
over the last few days, I have been running some very intensive test series with Server 2019 and also 2025 to determine/compare their behaviour with a specific workload.
During the tests, for example, I also wanted to see how the systems behave with a network load with a block size of 4K with only one worker and one oIO.
I used the following test pattern for this.
NTttcp Sender:
NTttcp.exe -s -m 1,22,192.168.10.2 -l 4K -a 1 -t 60 -nic 192.168.10.1 -v
#NTttcp Receiver:
NTttcp.exe -r -m 1,22,192.168.10.2 -v -t 60
And I actually expected that NTttcp generate the data traffic following the conditions mentioned above, so that it looks like the following one ...
... but when I eavesdropped on one of the test runs on the transmitter side with Wireshark, I had to see the following ...
... in words, anything other than 4K with just one worker and one open IO. 😔
Why does NTttcp not adhere to the test specification in this case?
Best Regards from Germany
Alex
The text was updated successfully, but these errors were encountered: