Applies to: BLAZE

Issue Summary

High CPU or memory usage can cause live video interruptions, delays, or frame drops during recording. As a compensatory measure, the system temporarily handles overload conditions by switching live playback to I-Frame playback.

CPU overload occurs when CPU usage remains at or above 90% for 10 seconds or longer. Memory overload occurs when memory usage remains at or above 90% for 2 seconds or longer.

Common causes of increased system load include:

• Higher monitor/output resolution
   
• Dual-monitor configurations
   
• Large number of live channels displayed
   
• Live output of the maximum number of channels at high monitor resolution (often the heaviest load)

This article explains how to check CPU/memory load and configure the system based on your primary monitoring environment (local or remote).

Resolution

Regularly check the CPU and memory usage indicators in the upper-right corner of the screen and adjust settings when overload conditions persist.

To reduce load, monitor the CPU/memory status and try one or more of the following:

• Reduce the number of channels included in live display/streaming
   
• Lower the monitor/output resolution to reduce rendering and decoding load
   
• Simplify live layouts, avoid displaying many channels at once, and keep only essential views active (if applicable)

These adjustments help restore smooth live video and reduce performance-related instability.

Optimize Your Primary Monitoring Environment

How you primarily monitor the system affects the best performance configuration.

If remote live monitoring is the priority, reduce unnecessary local processing:

• Exclude or minimize local live output.
   
• Set the live output to the Home path (default view) so the Appliance uses fewer resources on local rendering.

If local real-time monitoring is your priority, configure as a mandatory local environment.

• Minimize local live output.
   
• Configure various layouts assembled with the necessary cameras for each purpose, using them only for the required live output so the Appliance uses fewer resources on local rendering.