Metasys Performance Issues – High CPU, Slow Response

Problem

Metasys UI is slow to load, server is sluggish, and CPU usage stays above 70% even when no one is using the system. Trends and graphics take 10+ seconds to open.

Root Cause

Database too large, excessive polling, too many historical events being logged, or old database files bloated with cleanup.

Solution

1. Check Database Size:

   • In Metasys Database Manager, view the archive database size (usually C:\ProgramData\JCI\Metasys\)
   • If larger than 50 GB, it's likely bloated
   • Archive old data to external storage or delete unnecessary trends

2. Reduce Polling Frequency:

   • Identify high-frequency polled devices (should be max 5–10 sec intervals)
   • Increase intervals for non-critical devices to 30–60 seconds
   • Use change-of-value (COV) instead of interval polling where possible (reduces network chatter)

3. Reduce Trend/Event Logging:

   • Audit which points are being trended (every point shouldn't be logged)
   • Reduce trend buffer sizes in configuration
   • Archive old trend data to external database (SQL Server can compress and store years of data efficiently)

4. Defragment Database:

   • Stop Metasys services
   • Use Metasys Database Manager to "compact" or "rebuild" the database
   • This reclaims wasted space and improves query performance

5. Monitor CPU During Peak Hours:

   • If CPU is still high after reducing polling:
     • Check if virus scanning is active (exclude Metasys folder from real-time scan)
     • Look for network/disk I/O bottlenecks
     • Consider server hardware upgrade (RAM, SSD)

6. Reindex Database:

   • In Database Manager, run a Rebuild Indices job overnight
   • Improves query performance significantly