Hi All;
What could be the reason very hight CPU utilization after only start services CV. This is server with 10 x 2TB disk and millions small files. This is fresh installaton (version 11.20.40).
Regards;
Pawel
Best answer by Pawel
View originalHi All;
What could be the reason very hight CPU utilization after only start services CV. This is server with 10 x 2TB disk and millions small files. This is fresh installaton (version 11.20.40).
Regards;
Pawel
Best answer by Pawel
View originalHi Pawel,
Would you be able to give me some further information.
Regards
Blaine
Thanks!
Hi
While we’re awaiting your confirmation of which server this is, I want to also mention the following:
https://documentation.commvault.com/commvault/v11/article?p=11_20_46.htm
Maintenance Release 20.46 is available which has a patch for performance issues and will include a patch found in 20.41 as well.
Commserve may use high memory and CPU | 3646, 3647, 3648
|
Automatic backup copy schedules may cause SQL server process to consume 100% CPU. | 3457, 3458 |
In addition to these patches, if your Commserve is a VM this might be a good time to confirm that it is utilizing the best provisioning for your environment:
https://documentation.commvault.com/commvault/v11/article?p=2801.htm
Note:
- For SQL Server 2014, license is limited to lesser of 4 sockets or 16 cores, or whichever comes first.
- For SQL Server 2016/2017/2019, license is limited to lesser of 4 sockets or 24 cores.
- For SQL Server scheduler, use NUMAs for distributing or scheduling SPID load.
- For VMs with more than 4 sockets, SQL Server uses only the first 4 sockets and considered as a bad VM configuration.
- Each VM socket should have its own NUMA association for SQL Server Schedulers and CPUs with more than 4 per NUMA.
- SQL Server VMs should have matching, dedicated physical CPUs on the VM Host. The VMs must not be shared for best performance.
- SQL Server VMs for database IO drives should have 30 IOPS or better performance
In addition to confirming the provisioning of 50% available memory to SQL server and an ideal cpu configuration for SQL server (strictly speaking for the Commserve server) I also recommend updating to sql server 2014 or 2016 if you are running an older version on the Commserve as we have seen confirmed stability and performance improvements here.
https://documentation.commvault.com/commvault/v11/article?p=7665.htm
I agree with all the potential paths mentionned above to follow.
I’d add that if it’s a Filesystem agent client with the Advanced options to track changes on the files like this :
If you have lots of files changed after a reboot, or update, this could occur, until the scan is complete.
But, we need to get more background information to properly assist
Hi
Following up to confirm if you have had a chance to review and if you can confirm if this is for the commserve or a different server
Hi All;
I am sorry for delay in answer, thank you for all suggestions , I tested all this options but finally I was opened the SR.
The problem was resolved when I set this additional settings:
https://documentation.commvault.com/commvault/v11_sp20/article?p=7879_1.htm
https://documentation.commvault.com/additionalsetting/details?name=DisableFileIOMonitor
Regards;
Pawel
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.