CPU Stress free value sky high

[redsnapper76]

Header 1	Mhz
Configured	17000
usage	15000
demand	19000
effective demand %	237
stress free demand	36000
recommended size	40000

Hello,

I have difficulty trying to understand the following.

If the demand is around 19000 Mhz, why is the stress free demand, and recommended size so high?

Also effective demand is 237%

Here it proposes Stress free value 36 Ghz

[daphnissov]

The demand pattern in this workload has changed somewhere after July 24th which may be why you're seeing this calculation. The time window on stress badge shows the last 30 days while the raw metric screenshots you've provided display the last 60. The spike between July 24th and July 31st shows about a 100% gain in the effective demand for this system, so what changed? Was it something inside the VM? Was a new version of the application installed or a patch applied?

[redsnapper76]

Hello,

Sorry forgot to mention, this is on a resource pool

[daphnissov]

The same sort of concepts apply. Do you have a limit on CPU on your resource pool and have then added additional VMs, upsized existing ones, or changed application workload patterns?

[redsnapper76]

Found it

There was one big job on SQL Server that provoked this

How-ever it remains on that level since 25/07, which is confusing as there is no stress level since 25/07

Is there a way to do a recalculation faster or is it always 30 days?

When we create reports for a customer, this value comes up which is not clear to customer

[daphnissov]

The metric is going to show a 30-day window, but you can change how stress is calculated in the policy that applies to this resource pool. Edit the policy that applies and add an override for the object type of resource pool. Unlock the Stress sub-badge to make changes. Change the sliding analysis window calculation method be an interval greater than 60 minute peaks and save the edited policy.