Benchmark: Compute Checks
Thrifty Compute Benchmark
Thrifty developers eliminate their unused and under-utilized compute instances. This benchmark focuses on finding resources that have not been restarted recently, have old snapshots, have high disk IOPS and have large, unused or inactive disks.
|The number of average read/write ops required for disks to be considered frequently used. This value should be higher than
|The number of average read/write ops required for disks to be considered infrequently used. This value should be lower than
|The maximum IOPS allowed for disks.
|The maximum size (GB) allowed for disks.
|The maximum number of days virtual machines are allowed to run.
|The maximum number of days snapshots can be retained.
|The average CPU utilization required for virtual machines to be considered frequently used. This value should be higher than
|The average CPU utilization required for virtual machines to be considered infrequently used. This value should be lower than
Browse dashboards and select Compute Checks:
Or run the benchmarks in your terminal:
steampipe check azure_thrifty.benchmark.compute
Snapshot and share results via Steampipe Cloud:
steampipe loginsteampipe check --share azure_thrifty.benchmark.compute
- Disks attached to stopped virtual machines should be reviewed
- Disks with high IOPS should be resized if too large
- Disks should be resized if too large
- Compute disks with low usage should be reviewed
- Disks should use standard snapshots
- Unused disks should be removed
- Old snapshots should be deleted if not required
- Long running virtual machines should be reviewed
- Compute virtual machines with low CPU utilization should be reviewed