Knowledge base:
Warning for Hardware limit exceeded
Posted by Pieter Vandercammen, Last modified by Pieter Vandercammen on 28 March 2018 06:05 PM
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, but the response is always the same. We'll first explain the reason and next delve into the causes and give hints to avoid this error in the future.

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 this step fails, the flow isn't started. The other flows on the system aren't affected and the rest of the test continues.

Such an fault is list in the Warning section of the test-report. No througput results are available, these have the value value n/a. Of both there's an example below.

To avoid this warning in future runs, you can take following actions.
  1. When it's caused in a single scenario, you'll need to either

    • Lower the bandwidth of the conflicting flow. The total show be remain below the hardware interface limit.

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

  2. When sharing the system, you'll need to coordinate to avoid exceeding the interface limit.

(0 vote(s))
Not helpful

Comments (0)

We to help you!