ADS memory sizing and performance in DC RUM 2017

Applies to DC RUM 2017

When the built-in ADS memory limit is reached, a red triangle appears on every report that is run while on the ADS. You can take some practical steps to try to reduce the load before you consider upgrading your system.

Reducing the load

  1. Turn off ADS data collection for software services.
  2. Make sure that no other memory-consuming processes are installed on the ADS machine. This might happen if unrelated applications are installed on the system for purposes other than hosting the report server.
  3. Ensure that the AMD is configured so that the number of observed dimension values does not expand unnecessarily.
  • The ADS can experience memory problems if the observed values of a dimension used for measurements—such as users, URLs, or sites—are unusually dynamic, particularly when this happens over a long period of time. For example, if the user name is set to be the session ID string, this will be unique for every new user session. Consequently, each day the ADS will receive a new batch of distinct user names, eventually causing the set of observed users to grow dramatically.
  • If you configure the AMD so that every URL string is registered as unique—by, for example, including the time stamp as a page parameter—the list of unique URLs will grow very large and cause memory problems on the ADS.
  1. Use ADS configuration mechanisms to reduce the load by using ranges (for example, server or client ranges).

Migration and upgrade

  1. If you have installed the CAS and ADS on the same machine and if either needs more memory, consider installing them on separate machines with additional memory. The same is true with SQL Server when it is installed on the same machine.

  2. If you are using a 32-bit report server, consider upgrading to a 64-bit report server.
    The best way to avoid the memory limit issue on 32-bit machines is to upgrade to 64-bit ADS on a 64-bit machine.