High CPU utilisation (over 95%) while executing Automation for Jira Rule
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
There is high CPU utilization (over 95%) while executing a global rule, with status THROTTLED in the Audit log :
Environment
Automation for Jira - Data Center and Server version 7.3.x.
Diagnosis
Check the: View performance insights page from your instance. It will provide an overall view of how the impacted rule has performed for the last 1 week/1 month.
What is the configuration for audit log expiry? ⚠️ In large instances, lots of audit logs can build up over time impacting your Jira database performance and clogging up your disk space.
Is there a spike in CPU utilization only upon execution of the THROTTLED rule? How is the overall Jira performance? Is there any slowness while performing any other activity in Jira?
If the CPU utilization is going high only upon execution of automation rules, the View performance insights page should be reviewed to ensure that there were no other A4J rules which were getting throttled.
Cause
There could be multiple reasons, including:
There are A4J rules which are getting throttled and CPU utilization is going high.
Problematic rules are not being in use. During execution of these redundant rules there is a spike in the CPU usage.
Audit log expiry is set to Never expire audit items
Solution
Any of the problematic rules that were not in use should be disabled to improve A4J performance.
Head to the Global Configuration section, then enable audit log expiry by sliding the audit log expiry period to your preferred value: configuration for audit log expiry.
Configure the rule in a way that reduces the performance impact on Jira, like setting up the rule on a scheduled basis using a "Scheduled trigger".
Note: Plan your rules before creating them: Optimize rules.
Was this helpful?