Execute Performance Counter Routines In The Separate Process

Background

The Argent XT Relator Basic tab has an option, “Execute Performance Counter Routines In The Separate Processes”. Customers are sometimes unsure when to use this option.

If this option is checked (the default setting), Argent uses a separate process for each performance-monitoring task. You will notice that when using this setting, you will see several processes in the Windows Task Manager on your Argent server, each using the executable “AMC_NonSharedPerf.exe.” For monitored Nodes on the same LAN as the Argent server, you should leave the default setting.

When the monitored Nodes are on a WAN link however, you should uncheck this option, allowing Argent to use a shared process for retrieving performance data. The executable you see in the Windows Task Manager is “AMC_SharedPerf.exe.” Using a separate process for each performance-monitoring tasks incurs unnecessary network bandwidth use.

Architecture Choices

When monitoring nodes over limited bandwidth links the architectural choices are, in preferred order:

Mother / Daughter
Remote Monitoring Engine
Centralized Monitoring using AMC_NonSharedPerf.exe

In cases where there are only a few remote nodes, Mother/Daughter and Remote Monitoring Engine would be overkill.

Argent recommends splitting nodes into separate monitoring groups based on physical location, allowing you to configure Relators for LAN nodes using Execute Performance Counter Routines In The Separate Processes and another for WAN nodes with the setting unchecked.