So, this is a partitioned server. It has an allocation of 1.3 CPUs. I'm assuming therefore that there are other partitions defined, and perhaps a little spare CPU on the chassis as a whole. If the partition is capped, then it will use up to 1.3 CPUs and no more. If it is uncapped and there is spare CPU then it will burst through the limit and you will see the value for entitled CPU on
sar or
vmstat exceeding 100%.
If you take the cap off the partition and other servers are busy, they will be guaranteed to get their allocated CPU as a minimum, however as already pointed out by
Zaxxon, you are not CPU bound (95% entitled capacity)
Consider partitions:-
- 1.3 CPU shared
- 3.0 CPU shared
- 2.0 CPU dedicated
- 1.7 CPU shared
Server has 8 CPUs. Two are dedicated, so out of the reckoning. If the shared CPU partitions are all uncapped, then if the other two are idle, the busy one could get 6 CPUs. If all are busy, then they will be limited as shown. If partition 4 is idle and 1 & 2 are busy then they will compete for the spare CPU (after both have reached their entitled CPU limit) and you can weight them to show a preference.
You may be better just upping your CPU allocation a little then re-activating the partition (not just a reboot) else your end user will get used to having the full spare CPU available and then complain when it's in use elsewhere on the chassis. Is there another partition you could squeeze down, but take the cap off because it is rarely busy?
We have our set as 0.1 CPU, production uncapped, test/dev capped.
I hope that this helps.
Robin
Liverpool/Blackburn
UK