Consolidate VM rightsizing patterns into 'Rightsize compute to match utilization'

[russelltrow]

Title

Rightsize compute to match utilization

Version

1.0

Submitted By

dubrie (original author of both source patterns)

Published Date

2022-11-10 (carried over from the originals; to be confirmed by the patterns working group)

Intent

Match allocated compute to measured utilization, by resizing a VM or choosing a better-fitting pre-configured instance type.

Tags

compute, monitoring, size:small

Problem

match-utilization-requirements-of-vm and match-utilization-requirements-with-pre-configured-server are near-identical: same author and date, and verbatim-identical Description, SCI Impact, Assumptions and Considerations. Only the Solution differs. Both fail principles 5, 8, 10 and 11 in the August 2026 Operations analysis.

Solution

One consolidated pattern covering elastic VM resize and pre-configured SKU selection as two named techniques, rewritten against the current template and the 11 quality principles, with a new Cost Impact section.

SCI Impact

SCI = (E * I) + M per R

E decreases (higher utilization of remaining capacity, less idle draw); M decreases (fewer or smaller servers).

Assumptions

Utilization metrics cover a full business cycle; resources can be resized or migrated within availability requirements; peaks are absorbed by scaling or documented headroom.

Pros & Cons

• PRO: Removes duplicate content; stronger Assumptions and Considerations; adds cost impact.
• CON: Two URLs retire (redirected). Cost Impact is qualitative, with no quantified figures yet.

---

What changed

• Added docs/operations/capacity-management/rightsize-compute-to-match-utilization.md
• Moved the two originals to archive/operations/capacity-management/ (same approach as Archive low quality patterns #426), so the diff shows originals vs replacement
• docusaurus.config.js: old /catalog/cloud/... and /operations/capacity-management/... URLs redirect to the new page
• src/data/personas.ts: two rows replaced with one (edited by hand; regenerating pulls in unrelated stale AI-pattern changes)

For reviewers

• optimise-storage-resource-utilisation is not folded in. The wiki suggests it, but Consolidate Operations category duplicate patterns #434 treats storage as its own pair.
• Cost Impact is qualitative; an SME may be able to add real figures.
• Local site build not verified (missing @docusaurus/plugin-client-redirects in local node_modules); please rely on CI / preview.
• Needs at least one SME review before merge (per Consolidate Operations category duplicate patterns #434).

Part of #434 (pilot pair for #385).

🤖 Generated with Claude Code

[russelltrow]

@franziska-warncke I've actioned the first Operations patterns consolidation item.

I started with one of the simplest "VM rightsizing (near-identical)". Can you please review?