Use a dedicated node for Assets imports
This recommendation is shown when Assets imports are running on the same nodes that serve user traffic, and CPU‑bound imports are contributing to high CPU utilization and slower page response times.
Signals used
Details of how we detect this issue.
Conditions
The following conditions need to occur together:
At least one key experience, such as viewing or editing issues, shows degraded page load times (RFU).
During the same time window, one or more Assets imports were running.
A dedicated import node is not in use (imports run on the same nodes that serve user traffic).
There are CPU‑bound imports (imports where most of their total runtime was spent doing CPU work rather than waiting on I/O).
CPU utilization is high, and all nodes where the imports ran are saturated.
How we detect it
Signal | Details |
|---|---|
RFU degradation | We look for Ready for User (RFU) degradation - cases where key Jira experiences take significantly longer than their historical baseline. This helps us confirm that users are actually experiencing slower page loads, not just one-off spike. |
Assets import activity | We use Assets import completed events to see whether imports were running during the RFU degradation window. From these events, we determine if imports were CPU‑bound and how long they ran. |
Dedicated import node usage | We check whether Assets imports are already running on a dedicated import node. If all imports run on nodes that also serve user traffic, we treat this as not having a dedicated import node configured. |
CPU usage | We use JVM CPU metrics to identify CPU saturation on nodes where imports were running. All nodes that handled imports must be saturated for this recommendation to appear. |
Impact of imports vs. no imports | We compare RFU in the degraded window with a similar hour in a prior week where fewer imports were running. If RFU is better when fewer imports were running, we increase our confidence and raise the priority of this recommendation. |
Filters
When this issue occurs multiple times, we group occurrences under different time filters, for example a 24‑hour or 7‑day period.
In this case, for degraded experiences, we show the highest degradation from all occurrences in the selected time filter.
Recommended actions
Assign a dedicated node for running Assets imports
Set up a dedicated import node so that Assets imports run on infrastructure that does not serve user traffic.
Configure at least one node to act as a dedicated import node for Assets.
Ensure that import jobs are routed only to this node, so that heavy import work does not compete with user requests on other nodes.
You can configure this in Jira administration > Assets configuration. For details, see Installing and configuring Assets.
Was this helpful?