Review Compute Engine recommendations before resizing VMs
Review VM size suggestions against peak demand, compatibility and restart needs. Learn why estimated savings and empty recommendation lists need care.
Find answers to common questions about cloud and AI costs.
Review VM size suggestions against peak demand, compatibility and restart needs. Learn why estimated savings and empty recommendation lists need care.
Classify Cloud Run functions by documented version and console area before comparing costs. Keep pricing-family labels separate from API history and billed-SKU confirmation.
Use Lambda REPORT logs to spot unused memory, then compare runtime and errors before testing a smaller allocation. Memory headroom alone is not a savings estimate.
Check requested CPU, memory, storage and billable runtime for ECS Fargate tasks before estimating the cost of a sizing change.
Distinguish Stopped from Deallocated with a read-only Azure VM power-state check. Use PowerShell or ask an authorized colleague for the result.
Use AKS cost allocation and matching resource metrics to decide whether a cluster or namespace needs a capacity review, without treating allocated cost as proof of waste.
Compare a Compute Engine sizing recommendation with peak demand and memory evidence before approving a resize that could interrupt service or reduce performance.
List unattached Azure managed disks in one subscription, check when they became unattached, and review whether they are still needed before removal.