The Byteblower GUI generates several types of reports. The HTML and PDF reports from the ByteBlower GUI are limited by size of the test-run. On this page you'll a guideline to how large your tests can grow. This is a limitation by 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 right value using the table below.
   

   Graphing type	Multiplier	Lines
   FrameBlasting	1
   Latency	5	Minimum, Average, Maximum and Jitter twice
   TCP	5	Goodput, TCP throughput, round-trip time, transmit window, retransmissions
   Out of Sequence	1

3. Multiply the cost with the duration. The total should be less than 12000.

An example

For the example we use actions of 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 colunmn 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.

Creating larger tests?

The above guideline is only the HTML and PDF reports. For larger testruns you've got 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.