Review CPU usage of Marketplace apps in Confluence

This recommendation appears when we detect one or more Marketplace apps that are consuming high CPU cycles while the 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

For us to detect this issue, the following conditions need to occur together:

• At least one of the key experiences shows degraded ready-for-user (RFU) page load times.

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

• Apps with unusually high CPU consumption during the same period.

フィルター

When the issue occurs multiple times, we group their signals under different filters. For example, Last 24 hours or Last 7 days. In this case:

• In the Degraded experiences section of the recommendation, we show the highest degradation from all occurrences.

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

頻度

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

推奨されるアクション

We recommend that you review and investigate the identified apps. The process 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. 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, and fix them.

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.

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 the 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.