# Interpret CPU and RAM spike percentages before resizing endpoints

> What do endpoint resource spike percentages measure before a hardware change is proposed?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-231-interpret-cpu-and-ram-spike-percentages-before-resizing-endpoints/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:28:05+00:00
- Modified: 2026-09-10T01:20:46+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 1 minutes

## What you need to know

What do endpoint resource spike percentages measure before a hardware change is proposed?

## Potentially affected

Separate a physical-device investigation from a Cloud PC sizing decision. Identify the relevant period, workload, and whether the report contains sufficient measurements for that endpoint.

## DSE recommendation

Review CPU and RAM separately before proposing replacement or resizing.

## Article

## Source facts

The resource-performance report covers Windows devices and Windows 365 Cloud PCs. CPU utilization above 50 percent and RAM utilization above 75 percent count as spikes. The displayed spike percentages compare spike time with device usage time and are averaged over 14 days. The report combines CPU and RAM spike-time scores into its overall performance rating. [Microsoft Learn](https://learn.microsoft.com/en-us/intune/advanced-analytics/resource-performance).

## Applicability

Separate a physical-device investigation from a Cloud PC sizing decision. Identify the relevant period, workload, and whether the report contains sufficient measurements for that endpoint.

## DSE recommendation

Review CPU and RAM separately before proposing replacement or resizing. Compare an affected device with a suitable workload cohort and ask the user when the slowdown occurs. Use the reported interval to guide deeper investigation of the application and device timeline. Treat the score as a prioritization input, not proof that adding hardware is the only useful remedy.

## Verification

Collect an approved observation during the reported workload and reconcile it with the resource identified by the report. Document whether the issue is sustained, intermittent, or not reproduced. Test the proposed adjustment on a bounded example and compare user experience as well as the relevant metric. Preserve the original configuration and measurement window so the owner can distinguish an improvement from a change in usage or population.

## Official references

[Microsoft Learn: Resource Performance Report](https://learn.microsoft.com/en-us/intune/advanced-analytics/resource-performance).

## Primary reference

- Name: Resource Performance Report - Microsoft Intune | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/intune/advanced-analytics/resource-performance
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Interpret CPU and RAM spike percentages before resizing endpoints,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-231-interpret-cpu-and-ram-spike-percentages-before-resizing-endpoints/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.