The most common reasons for seeing high CPU in Object Store are:
1. The ProxySG has a bad disk or a disk is missing.
The Object Store's main functionality is to create, remove and maintain objects on disk. If the ProxySG has a bad disk or a missing disk this could affect Object Store's ability to function properly. The ending result could be the high CPU like in the above example.
To check if this issue is the cause of the high utilization, verify the state of the ProxySG's disks by using the ProxySG's management console GUI. The disk states are in the Statistics->Health Monitoring->Status tab. The states are "present," "not present" or "empty," or "bad." Any disks that are listed as "bad" should be replaced as soon as possible. Besides bad disks, missing disks could also pose a problem. To verify if a disk is missing please confirm which disks are present in the ProxySG's chassis, then verify from the management console GUI whether the disks are "present" or "not present." Any disks that are physically in the ProxySG but are showing up as "not present" should be replaced as soon as possible.
2. The ProxySG is processing excessive bandwidth.
Each ProxySG platform is sized to be able to process a certain amount of bandwidth. If that bandwidth is exceeded the result could be high CPU in Object Store because it is very busy reading, writing, and processing objects on disk.
Using the management console, verify the bandwidth using the Statistics->Traffic Mix section. Confirm if the processed bandwidth for the SG is "typical" for the ProxySG or if it corresponds to the CPU spikes. If there is a correlation, lower the amount of bandwidth that the ProxySG processes and see if the CPU drops.