Sizing APM Central instances

APM Central combines the Console, Real User Monitor, and Performance Analytics Engine on the same virtual machine. APM Central is sized according to the following table:

APM Central sizes

* An additional 100 GB minimum on a secondary disk is recommended for storing traffic data. For additional information, see the APM Central storage requirements in the System requirements.

As more traffic is added to the system, you must re-evaluate APM Central capacity to ensure that the increased load is not a problem. 

Sizing for concurrent pages and sessions

The size that you choose to deploy might depend on the number of concurrent sessions or pages that APM Central must process:

  • Low — 50,000 pages or 150,000 sessions
  • Medium — 70,000 pages or 210,000 sessions
  • High — 90,000 pages or 275,000 sessions

Increased traffic volume usually correlates to more users requesting more web pages. However, a given site can have a high traffic rate and a low number of users (or vice versa). So, independent of the traffic volume, you might have to adjust the resource allocation of APM Central to accommodate page- and session-tracking needs.

Note

To "rebuild" pages and sessions, APM Central uses memory caches, the size of which determines how many simultaneous page requests and simultaneously active users that the system can track.

Related topic

BMC-Real-End-User-Experience-Monitoring-system-architecture

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*