NAM system sizing and performance factors

The following factors influence the size and performance of the NAM system.

Deployment configuration

The deployment topology is defined by the points in the network where you need to insert the various NAM components, particularly the NAM Probes. For more information, see NAM deployment examples.

Remember not to place the NAM Probe in high traffic throughput areas, such as an Internet backbone segment.

Traffic volume per traffic profile, as it relates to NAM Probe capacity

The traffic profile corresponds to the protocol analyzer that is used by the NAM Probe to parse this type of traffic. Knowing the load per traffic profile helps you estimate the required number of NAM Probes and determine the best NAM configuration.

Tip

Do not install a NAM Probe in environments with unknown traffic volumes.

Number of sessions and users

Traffic complexity, determined by the number of sessions (bi-node conversations) and distinct users present in the analyzed traffic, is used in NAM Server and NAM Probe sizing.

Traffic profiles to be analyzed and type of analysis

This factor consists of the components of the traffic that you want to analyze and the level of detail for which to analyze that traffic. See the NAM protocol-specific documentation for details on the type of analysis available for each type of traffic.

One of the most important deployment decisions to make is the required type and level of analysis. This is because the analysis type and level are directly related to the NAM configuration to be used, and the correct configuration is critical to system sizing. Configure the system to deliver only the information you require.

Tip

Do not attempt to measure all metrics for all the traffic all the time. In most cases, this approach will not support your monitoring objectives and will negatively affect system performance, while at the same time hiding the relevant data.

Database response speed

SQL I/O disk performance is the greatest capacity limiting factor for NAM Server and ADS. Do not offload the SQL database from the NAM Server or ADS machine to another server unless the other server offers faster disk I/O speed and, if the other server is shared, the effective available I/O on the other machine is at least the same as that of the local hardware. For more information, see SQL Server offload - advantages and disadvantages.

After you assess the above factors, you can plan an estimate of the size of the required deployment by estimating the required number of specific NAM components required.