Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Discovery resource utilization

Standard transactions on Windows and UNIX generate various amounts of network traffic, depending on what is being discovered.

These tables show the bandwidth consumption for each data flow segment of a typical discovery using probes and patterns over different operating systems.

Device TypeMID > InstanceInstance > MIDMID > TargetTarget > MIDTotal
Windows 20160.1049660.1012710.777392.3643533.34798
Windows 20120.1263270.079281.1771463.707515.089804
Windows 20080.1418160.1046741.0326733.5947844.873947
Windows 100.0914660.0756010.6423132.2211033.030483
Linux CentOS0.1642320.1113760.1487420.6901171.114467
Mac OSX0.1037070.0683020.0216810.4613650.655055
HP-UX0.1203580.1066760.0426690.1011490.370852
Solaris0.1305510.0994140.0602430.3466050.636813
Cisco UCS Switch0.0296550.0274650.0949180.0974440.249492
F5 Load Balancer0.0439350.036890.0171790.0121320.110136
A10 Load Balancer0.0466310.0322660.0183130.031820.12903
EMC Storage0.47760.3738281.2159544.7419266.809308

The following table shows the bandwidth comparison between an initial discovery for three-tier applications and for each subsequent discovery. Bandwidth is broken up into the three tiers: UI (Apache), application (Websphere), and data (Oracle). This measures the total data transfer for each discovery run once for a device class.

Device TypeMID > InstanceInstance > MIDMID > TargetTarget > MIDTotal
Three-tier application - Initial discovery0.7128290.6788627.0846789.43018117.90655
F5 Load Balancer   0.0171790.012132
Apache on Linux   0.5401611.107108
Websphere on Linux   0.7294031.165112
Oracle on Windows   5.7979357.145829
      
Three-tier application - subsequent discovery0.1508820.1074092.5365350.5601223.354948
F5 load balancer   0.0013470.012132
Apache on Linux   0.1363660.79392
Websphere on Linux   0.3410420.11365
Oracle on Windows   2.057780.354948

This table shows discovery of different OS types using patterns. This measures, in megabytes, the total amount of data created and the total amount of data in subsequent scans for each device.

Device MID > InstanceInstance > MIDMID > TargetTarget > MIDTotal
LinuxCreate0.390.4860.0980.2731.247
 Update0.3820.4990.0930.2641.238
Windows ServerCreate0.2890.3165.6288.50814.741
 Update0.2730.3065.6218.45814.658
SolarisCreate1.2221.40.3830.9173.922
 Update1.241.42.399.6753.734
HP-UXCreate0.1760.2220.0630.130.591
 Update0.1780.2470.0620.1280.615
Citrix NetscalerCreate0.4241.9190.0190.0422.404
 Update0.3550.6190.0160.0411.031
F5Create0.0870.1350.0260.0470.295
 Update0.1320.1710.0260.0470.376
L3 SwitchCreate0.1720.1250.2820.4781.057
 Update0.1780.1260.2820.4791.065

Note: These measurements were taken with base operating configurations. Your local system results may vary.

CPU Usage examples

Examples from CPU Usage will vary among the matrix of thousands of combinations of Operating Systems, chip sets and specific loads for each system.

Your mix of these variables will determine your unique level of CPU consumption.

You can identify unique builds using internal templates and discover them by watching the performance impact, or lack of performance impact that your Discovery tool has on your system.