Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Right-sizing over-provisioned servers: reclaiming CPU and memory safely

Technical article
Hosting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

A server is oversized when its busiest periods across a full business cycle still leave a large share of its processors and memory unused. To reduce it safely, collect peak figures over that whole cycle, including month-end and the end of the financial year, take away a modest step rather than the whole surplus, book the change with a planned restart, watch the next peak, and keep the old size written down so it can be put back quickly. On a busy VMware host, removing processors a server cannot use can also help its performance, not just its cost.

Why it matters

Where a hosting plan charges by allocated processors and memory, an oversized server costs money every month. Servers can grow over the years through "just in case" requests that nobody revisits. But reducing a server on the strength of a quiet week is how a business discovers, at end of quarter, why it was that size. The method matters more than the saving.

How it works

Evidence over a full cycle

Cloud tools that recommend smaller sizes make the evidence period explicit. Microsoft's Azure Advisor notes that "The available lookback periods are 7, 14, 21, 30, 60, and 90 days". AWS Compute Optimizer similarly lets you "Configure a specific lookback period option" and "Adjust both the headroom and threshold of your CPU utilization".

Broadcom's own procedure asks for baseline data "over a representative 24-hour period". Our recommendation is deliberately stricter, because a day, or even 90 days, can miss the yearly peak of a business server: before reducing anything, check that your evidence covers the busiest events the server faces, such as payroll, BAS, end of financial year or the season. If you have only a quiet period, wait. Our published article Sizing a business application server from measurements, not the vendor's minimum covers collecting figures across a full business cycle.

What oversized looks like

Broadcom's rightsizing guidance for ESXi 8.0 gives the signals:

Two other figures point the other way, at the host rather than the server. Broadcom notes that "Sustained high ready time generally signals CPU contention at the host level rather than undersizing of the individual VM", and that "Non-zero ballooning indicates host memory pressure has caused ESXi to reclaim memory from the guest". If the server is slow and these are high, look at the host as well as the server: the provider must address a busy host, and shrinking one server will not cure that on its own, although rightsizing oversized servers can reduce the total demand on the host. Diagnose both rather than assume either.

Your provider can read these platform figures; ask for them alongside the Windows peaks. Our published article CPU overcommit in hosted clouds: ready time and NUMA explains ready time in more depth.

When fewer processors can help

It sounds wrong, but Broadcom advises: "Configure neither more vCPUs than the workload can effectively use, nor fewer than it needs." It explains that "extra vCPUs add scheduling overhead and can reduce performance on heavily loaded hosts". The gain, where there is one, comes on heavily loaded hosts and shows as high co-stop; on a lightly loaded host there may be none.

What to choose and why

A safe reduction method

  1. Record the current size and the reason it was set, if known.
  2. Collect a full cycle of peaks: sustained processor peak, memory in use, and the platform figures above.
  3. Check what is special. A database server's memory figure can look full while it is working normally (see below), so it is not evidence either way. Ask the application owner about licence terms tied to processor counts.
  4. Cut one step. For example, from eight processors to six, not to four; from 32 GB to 24 GB, not to 16 GB.
  5. Book a planned restart. Broadcom's procedure says "Changes to vCPU count, memory size, or CPU topology require the VM to be powered down".
  6. Watch the next peak. If users notice slowness, restore the recorded size; that is also a shutdown change, so have a window ready.
  7. Repeat only if the next cycle again shows a clear surplus.

Illustrative example

A professional-services firm's remote desktop server has 16 processors and 64 GB. Over a year including June, its sustained processor peak is 35 per cent and memory in use peaks at 30 GB, with low active memory on the platform charts. The firm reduces to 12 processors and 48 GB in a Friday evening window, watches the next month-end and BAS quarter, sees peaks of 45 per cent and 31 GB with no complaints, and stops there. The example is illustrative.

Risks and limits

Sources

Opened 15 November 2026; Broadcom 438023 and the SQL Server memory page reopened 16 November 2026.

Related articles: CPU overcommit in hosted clouds: ready time and NUMA; Sizing a business application server from measurements, not the vendor's minimum.

Related service: Managed support.

Learning notes

  • Collect peaks across a full business cycle before reducing anything.
  • Low active-to-allocated memory suggests oversizing; co-stop above about 3% per vCPU suggests too many processors.
  • High ready time or ballooning points at a busy host; diagnose host and server together, since shrinking one server alone will not cure host contention.
  • Extra virtual processors can slow a server on a busy host.
  • Reduce one step at a time, in a planned window, and watch the next peak.
  • Write down the old size so it can be restored quickly.