-
Title
Litespeed GatherJobStatistics job uses high amount of CPU -
Description
LiteSpeed GatherJobStatistics job uses high amount or percentage of CPU.
-
Cause
Defect -
One thread waited for another up to 10 min (in the engine code) with CPU using by 100% in some, not all, cases.
-
Resolution
STATUS:
Fixed in Version 7.02 of LiteSpeed.
-
Defect ID
CR95312 -
Additional Information
Check if the the following workaround will help:
1. Verify if the SQL instances are valid operational SQL instance for the server the registry files came from (IE: hosted on that server)... If not, then please delete the registry key (Please export the key first before deleting)...
Example registry key to delete:
HKEY_LOCAL_MACHINE\SOFTWARE\Imceda\SQLLiteSpeed\Engine\ActivityServers\<Server name$Instance name>S\<Server Name>
2. Disable the LiteSpeed_GatherJobStatistics. Rerun the Instance Configuration and select "Do not configure acitivity logging at this time".
This setting will allow the LiteSpeed backups, restores, maintenance plans, etc. but will not utilize the LiteSpeed Activity Service, which is what calls the LiteSpeed_GatherJobStatistics stored procedure.As long as the LiteSpeed for SQL Server Update Native Backup statistics job and/or the LiteSpeed Activity Service aren't running, the process won't run.
3. Schedule the update to run when the server isn't busy (once or twice a day, depending on your needs).