Recently came across an issue with Orchestrator performance in a customer environment. Orchestrator was showing symptoms of slowness and latency when loading or performing daily tasks. We also found disk utilization alarms in the alarms tab.
Upon further investigation, it was found out that Orchestrator was not provisioned initially per the best practices.
To help improve performance and overcome latency, we recommended to change the provisioning type from thin provision to thick provision. We also recommended to increase the disk space (procedure not covered here) to make sure Orchestrator is provisioned with sufficient disk space for the future.
It is always recommended to assign sufficient disk space when provisioning the Orchestrator first time to avoid disk utilization alarms.
Below is a screenshot of disk space utilized over 50% that was generating alarms in customer network.
Below is a screenshot of Orchestrator disk space after it was increased.
After changing Orchestrator provisioning from thin to thick and increasing the disk space, customer observed noticeable difference in performance and improved experience. This also resolved disk space alarms for them.