Performance Tuning Guidelines for CEM
search cancel

Performance Tuning Guidelines for CEM


Article ID: 18442


Updated On:


CA Application Performance Management Agent (APM / Wily / Introscope) INTROSCOPE



The performance of TESS is very slow, what performance parameters can be checked? How can the performance be improved?


If you find your CEM TESS (TIM Collector) to be performing slowly, check the following parameters and tune them to see if there is a performance improvement.

  1. Check to see if daily stats aggregation is completing successfully and running well.

    • Review the Daily Aggregation logs. If the Daily Aggregation is lagging, go to /etc/wily/cem/tess/tomcat/webapps/wily/WEB-INF/classes/ on your TESS-MOM (TIM Collector) server and change stats.intervalsAggregatedPerIteration=1 to 4 in addition to the other changes suggested below.

  2. Check to see whether CEM is running in Enterprise Mode or E-Commerce mode. For applications using more than 5000 users, we recommend running CEM in E-Commerce mode.

    The total number of users can be gathered by executing the following query for a Postgresql database:

    • Login to Postgres:

      • psql -d cemdb -U admin cemdb

    • Execute the following queries:

      • select count(*) from ts_users;

Check the size of CEMDB (APMDB). A large Postgres database size can cause a slow TESS (TIM Collector). if the database size is very large, run the manual Postgres Vacuum command to free up Postgres table space.

Increase the values of "Max-Fsm-Pages" in the postgres.conf file (/var/lib/pgsql/data/postgresql.conf )

Increase this setting to 24000000 and restart the database.

Check the following data retention settings on CEM and change to recommended values.

  • Go to CEM UI Setup>Domains>Data Retention Settings and check the current values. Reduce the value each day gradually to minimize adverse impacts on the APM Database.

  • Reduce the Hourly User Group Statistics. Lower the number by 30 each day, until it reaches 7, which is the Hourly User Statistics retention number.

  • Reduce Daily User Group Statistics. Lower the number by 30 each day, until it reaches 14, which is the Daily User Statistics retention number.

  • Reduce Weekly User Group Statistics. Lower the number by 4 each day, until it reaches 27, which is the Weekly User Statistics retention number.

  • Make Users inactive After: Lower this value by 30 per day, until it reaches a final value 30.

Once these changes are made, TESS (TIM Collector) will gradually start showing improved performance. If you still have performance issues, please contact CA APM Support by opening an issue at


Component: APMCEM