Maximum HTML report size

Introduction

The ByteBlower GUI generates several types of reports. The HTML and PDF reports from the ByteBlower GUI are limited by the size of the test-run. On this page, you will find a guideline for how large your tests can grow. This is a limitation of the graphing of the results over time.

For ByteBlower GUI v2.10 the limit of the graphical report is about 12 000 Graphing-Hr. This value is counted as follows:

  1. Count how long your test tests.
  2. Each type of graph in the report has a different cost. For each graph in the report, you'll need to multiply with the right value using the table below.
  3. Multiply the cost with the duration. The total should be less than 12000.
Graphing typeMultiplierLines
FrameBlasting1
Latency5Minimum, Average, Maximum, and Jitter twice
TCP5Goodput, TCP throughput, round-trip time, transmit window, and retransmissions.
Out of Sequence1


Example

For the example, we use actions of the below config. This scenario has 4 flows and 3 different types.


  • Duration of the test run:
    This test runs for 5 days. This can be read in the Duration column next to the name of the scenario.
  • Calculate the multiplier:
    This test run has a multiplier of 10 + 1 + 6 = 17
    • 2 TCP flows: 2 X 5 = 10.
    • 1 FrameBlasting flow: 1 X 1 = 1
    • 1 FrameBlasting + Latency flow: 1 X (1 + 5) = 6
  • Multiply
    17 X 5days = 17 X 5 x 24 Hr = 2040 Graph-hr   
    2040 Graph-hr < 12000 Graph hr.
    This test-run is ok.

In total, this test is below the reporting limit. You can thus generate HTML reports out of it.

Want to create larger tests?

The above guideline is only the HTML and PDF reports. For larger test runs you've got the following options:

  1. Split up the test-run into smaller scenarios.
  2. Only generate the CSV reports using the ByteBlower CLT.
  3. Use the ByteBlower API.