NAM Server memory sizing and performance

When considering NAM Server memory size and performance:

  • Compare the number of sessions, users, URLs, servers, and locations with the published limits.
  • Expect that memory will be consumed faster if your environment is atypical. For example, your installation may have memory issues if it has many more URLs than users. In such cases (especially when there is a large number of URLs, sites, applications, transactions, or tiers), cache limits can be reached earlier.

Reducing NAM Server load

There are several options for reducing the load on the NAM Server, such as limiting the traffic it can see and revising the monitoring requirements.

  1. Revise your monitoring requirements.
    Do not attempt to monitor too many entities or to configure too much detail to be reported. Re-assess your requirements to determine whether you can reduce your monitoring scope while still delivering the information you really need.
  2. Use IP ranges.
    Using IP ranges is an effective way to reduce the amount of traffic reaching the NAM Server.
  3. If possible, pre-filter some of the traffic before it enters the NAM Probe.
    For example, use the VACL, port mirroring filtering such as the SPAN port filtering feature of Cisco switches, or other filtering capabilities offered by network packet brokers such as Gigamon.
  4. At the NAM Probe level, minimize the volume and complexity of the traffic that is reported to the NAM Server by reducing the number or complexity of software services defined on the NAM Probe.
    To achieve this, reduce the number of sessions, users, URLs, servers, and locations to be handled by the NAM Server.
  5. Reconfigure the NAM Server to reduce the load.
    Consider using server or client ranges or URL and query aging. Restart is NOT required after modifying the NAM Server options.
  6. Create a load balancing cluster.
    Utilizing the NAM Server farm concept you can, for example, automatically load balance application users across all nodes in the cluster or void duplicating traffic across NAM Servers in large scale deployments. For more information, see Report Server Load Balancing.

Adding NAM Server memory

Adding memory after installing the NAM Server software will not automatically cause Java to use this new memory. For the memory to be utilized, you need to perform a number of configuration steps in the registry settings. When in doubt, contact Customer Support for assistance.

To adjust NAM Server memory size:

  1. Open the Registry Editor on the NAM Server.
    Select Start > Run, and then type regedit and click OK.

  2. Browse to the following registry key:

    HKEY_LOCAL_MACHINE/SOFTWARE/Adlex/Watchdog/<Server>

    where <Server> is the NAM Server.

  3. Double-click the JavaParms string in the right pane to open it for editing. The start of the string value contains the -Xmx value.

  4. Change the numerical value after -Xmx to the new amount in MBs. To convert GB to MB, multiply the number of GBs by 1024. For example, for 24 GB, the value is -Xmx24576M.

  5. After entering your new value in the registry, close the Registry Editor.

  6. Restart the NAM Server.