this is how TCP bandwidth-test works.
to test network use endpoints that are not your network infrastructure, just attached nodes to the path you want to test.
Err. No. It doesn't. I'm quite familiar with a variety of test equipment from industry recognised iperf at the low cost end through to spirent carrier class testing equipment.. Suggesting that the CPU of a test chassis should go to 100% when performing a 1 kbps test, well I'm just gobsmacked and i don't even know where to go with that.
If I'm testing to the limits of the test devices then sure the CPU is obviously going to top out, but when I am sending a piddly amount of data in an attempt to test at a particular rate, you're telling me it's still okay for the CPU to sit at 100% for 1Kbps rate ? What pray tell does the device do that requires it to use 100% of it's CPU when transmitting 1Kbps of TCP traffic?
More importantly, how the heck am I supposed to do a TCP test at any rate then without CPU starving the test devices for the duration of the test?