Background Traffic and Statistics
“Background traffic”, which is composed of both traffic flows and baseline loads, has one primary purpose: to model the effect of general traffic in the network on selected traffic of interest. This effect primarily takes the form of delay. In other words, background traffic causes additional delay for explicitly modeled traffic.
Of course, background traffic causes many other statistics besides delays and response times to be affected. Utilization and throughput on at least some links, for example, increase with additional traffic in the network. Average buffer sizes in routers would also be expected to increase. However, the background traffic system does not cause all of these statistics to be affected. Some statistics do not react to background traffic because of the ambiguities associated with modeling such effects. Others do not, simply because the background traffic architecture is a recent and ground-breaking invention that can still benefit from further integration into the model library.
While most important statistics that you will be interested in are integrated with background traffic, the purpose of this section is to alert you to those that are not so that you can comprehensively interpret simulation results. Also, while the statistics enumerated below do not reflect the effect of background traffic, the behavior of the simulation still does in most cases, in terms of injecting delay for explicitly simulated packets. In other words, this is primarily an issue concerning reporting of a specific subset of results, not simulation behavior. See Limitations of the Background Traffic System to determine which components do not provide additional delay modeling in response to background traffic.
Table 2: Statistics that Don’t Reflect Baseline Load System¹
- Queue and buffer sizes
- Global statistics of all types
- Server Task Load
- Shared Ethernet
- Switched and shared token ring and FDDI
- LAN Inbound, Local, Outbound, and Through traffic
- Statistics of Protocols at higher layers than IP (for example, TCP, UDP, Applications)
Note 1: check for latest information
The fact that certain statistics are not integrated with the background traffic system does not mean that these statistics are not accurate or meaningful. It simply means that these statistics have a different interpretation. Specifically, you should interpret these statistics as reflecting only the activities caused by explicitly simulated traffic (for example, traffic generated by application models specified on workstations and LANs). Finally, as integration of the background traffic system continues, you should check for availability of model library upgrades that would change the list above.