Why Pulse Turns On Performance Monitor in TM1

Users sometimes notice that TM1 Performance Monitor becomes active after Pulse starts monitoring an instance. This article explains why this happens and how to control it.

What Is the TM1 Performance Monitor?

The TM1 Performance Monitor (}Stats cubes) collects detailed performance statistics about TM1 server activity — thread counts, CPU, memory, active sessions, and more. When enabled, TM1 writes this data continuously to internal control cubes.

Why Pulse Activates It

Pulse relies on the TM1 Performance Monitor to collect the second-by-second monitoring data it displays in the Live Monitor. When Pulse connects to a TM1 instance, it sends a REST API request to enable Performance Monitor if it is not already running.

This is intentional — without Performance Monitor data, Pulse cannot display real-time CPU, memory, session, and thread metrics.

Impact on TM1 Performance

Enabling the Performance Monitor has a small but measurable overhead on TM1:

• TM1 writes stats to the }Stats cubes every second.

• On very large or heavily loaded TM1 instances, this additional write activity can add marginal load.

• In most environments the overhead is negligible.

Controlling Performance Monitor Behaviour

If you want to limit Performance Monitor to specific instances or reduce monitoring frequency, adjust the State Poll interval in Pulse Instance Settings:

1. Go to Administration → Instance Settings.

2. Select the instance.

3. Increase the State Poll interval (default: 1 second) to reduce how often Pulse polls TM1 for stats — for example, set it to 5 seconds for DEV instances.

4. Click Save.

Disabling Performance Monitor (Not Recommended)

Deactivating an instance in Pulse (Active = false) will stop Pulse from polling the instance and will allow TM1 to stop the Performance Monitor. However, this also disables all Pulse monitoring for that instance.

For production instances, it is strongly recommended to keep Performance Monitor enabled — the monitoring data it provides is central to Pulse's value.

Notes

• The Performance Monitor state (}Stats cubes) is stored in TM1 and persists between restarts. If Pulse enables it, it remains enabled until explicitly disabled via TM1 Architect or the REST API.

• Pulse does not disable the Performance Monitor when it stops monitoring an instance — TM1 administrators must do this manually if needed.