GitHub Projects: Basic Use Cases - Measuring Throughput
Posted by Craig Godbold, Last modified by Craig Godbold on 02 December 2021 05:15 PM
Basic Use Cases - Measuring Throughput
Having installed your ByteBlower system and checking that it works (quick self-test), you might be wondering what else you can do with it! There are endless possibilities so we will look at some basic use cases for the ByteBlower GUI to answer typical questions that testers have. One such example is:
This is a common question that a system user has and so in this article, we will guide you through a series of basic tests that can help you learn information about a system's throughput capabilities.
This article will cover →
1) UDP frame blasting approach
2) TCP approach
⇒ The LAN and WAN ports will be connected to different trunk ports on the ByteBlower server which will enable different scenarios to be tested.
STEP 1 - UDP Frame Blasting Test
We will start with a UDP test. Frame blasting allows us to focus on the amount of data that is received. This approach doesn't require any limitation on the transmission rate of the data.
1.1 Setting Up a First UDP Test
1.1.1 Dock the Ports
Here you will see that two ports have been created for you and they have been named LAN and WAN. You will also notice that they have small red crosses next to them. This means that they aren't docked yet.
When you open the 'Frame' tab, you can see that a frame has already been created. The frame is small (60 bits). Large frames tend to mainly load the network. Smaller frames allow for the checking of packet processing bottlenecks.
1.1.3 Frame Blasting
In this demonstration we are using a 1 Gbps port so the maximum speed is 0.95 Gbps.
The flow tab is used to finalize the traffic flow by choosing which port is the source and which is the destination.
When you open the 'Flow' tab, you will see that 2 flows have already been created → 1 UDP and 1 TCP.
The flow runs from the LAN to the WAN and for now, no latency measurement is being made. This flow will be used to run the first test.
1.1.5 Scenario - Running a Test
Up to this point, there has been no real communication or connection with the ByteBlower server. Once we run the test, the server comes into the picture
Go to the 'Scenario' tab and select the correct scenario from the two that have been created (Max_frame_blasting).
The flow is the one from the previous section. The test duration has been set at 30 seconds though this can be changed as wishes.