Knowledge base:
Warning for Hardware limit exceeded
Posted by Pieter Vandercammen, Last modified by Mathieu Strubbe on 22 February 2021 10:51 AM

This article explains the situation where a server is asked to generate more traffic than available by its hardware. There are a number of ways this can happen. We'll first explain the reason and next delve into the causes and give hints to avoid this error.

Exceeding the hardware limit is only possible with FrameBlasting. At the start of such a flow, the Byteblower Server attempts to reserve the requested bandwidth.
If there isn't enough bandwidth available :

  • the flow will be started using the remaining bandwidth.
  • the flow name will be marked in purple in the Realtime View and in the report.
  • a warning will be shown in the report.

Also, please note that the maximum bitrate is always only 99.99% of the link speed.
For example, on a 1Gbps link, you can send at a maximum speed of 999.9 Mbps.
The reason for this is that the clock on the server system and the clock on the network card are very slightly out-of-sync.

Below you can see an example of the warning at the bottom of the test report.

To avoid this warning in future test runs, you can take following actions:

  • When you are the only one using the ByteBlower system, you'll need to either

    • Lower the bandwidth. The total bandwidth must remain below the hardware interface limit.

    • When caused by multiple conflicting flows. You can spread them out so they don't run simultaneously any more.

  • When sharing the system with multiple users, you'll need to coordinate to avoid exceeding the interface limit.

(0 vote(s))
Not helpful

Comments (0)

We to help you!