Review Marketplace apps with high CPU load

This recommendation is shown when we’ve detected that one or more Marketplace apps are consuming high CPU cycles at the same time that page load performance is degraded. High CPU usage from apps can affect overall system responsiveness and contribute to slower user experiences across the instance.

Signals used

Details of how we detect this issue.

Conditions

The following conditions need to occur together:

• At least one of the key experiences shows degraded page load times (RFU)

• The operating.system.cpu.load metric for the system is degraded over the same time window when RFU degraded

• Then we identify the apps with unusually high CPU consumption during that same period

Filters

When the issue occurs multiple times, we group their signals under different filters, for example 24-hour or 7-day. In this case:

• For degraded experiences, we show the highest degradation from all occurrences

• For identified apps, we list the apps that contributed to this issue. For each app, we show its average share of CPU consumption across the observed occurrences

Frequency chart

Similar to filters, the frequency chart shows occurrences of this issue over time. It can help you spot patterns, for example apps causing high CPU load during peak business hours, after scheduled jobs run, or at specific times of the day or week.

Recommended action

Review and investigate identified apps

How to solve this issue will depend on the Marketplace app and what it does. Here are some actions you can take:

• Review the affected apps
  Check the apps shown in the recommendation. For each app, look for recent changes such as a new installation, an app upgrade, newly enabled modules, configuration updates, scheduled jobs, background tasks, automations, or integrations that may increase CPU usage.

• Look for patterns that line up with CPU spikes
  Identify whether high CPU usage coincides with specific user actions, scheduled tasks, synchronization jobs, indexing, reporting, automation rules, or traffic peaks. This can help narrow down whether the app is causing constant load or only spikes under certain conditions.

• Reduce or optimize CPU-intensive app activity
  Where possible, tune the app configuration to reduce unnecessary processing, lower job frequency, disable non-essential features, or move heavy tasks away from peak usage periods. If safe to do so, temporarily disable the app or a specific app feature to confirm whether CPU load improves.

• Contact the app vendor if issues persist
  If performance issues continue after reviewing configuration or usage, contact the app vendor. Share that you’re seeing high plugin.cpu.attribution values, the affected time window, the app’s observed CPU contribution, and any recent configuration or usage changes so they can help identify optimizations or fixes.