# How do I stop GPUs and notebooks sitting idle?

> Stop idle AI hardware wasting energy: start resources on demand, auto-stop idle notebooks, scale to zero out of hours and report idle GPU-hours.

Source: https://greenai.guide/how-do-i/stop-gpus-sitting-idle/  
Updated: 2026-11-19

## In short

Make on-demand the default: pipelines and training jobs should start resources when triggered and release them when done. Shut down idle notebooks and development GPUs automatically after a set time, scale non-production environments to zero out of hours, and report idle GPU-hours per team next to cost so the waste is visible.

## Steps

1. Make pipelines and training jobs start resources when triggered and release them when they finish.
2. Set notebooks and development GPUs to shut down automatically after a period of inactivity.
3. Scale non-production environments to zero outside working hours.
4. Give temporary environments an automatic destroy date.
5. Report idle GPU-hours per team alongside cost.

**An idle GPU still draws power and still ties up hardware that took energy to make.** Notebooks, clusters and test
environments set up for one experiment are easily left running between experiments, or forgotten.

## What should be on demand?

The Green Software Foundation's patterns for AI and agent workloads recommend running infrastructure only while it
works: serverless or on-demand execution for model development, pipelines and agents, so resources start when
triggered and stop when finished.

## What about development and test?

Microsoft's Azure Well-Architected guidance says to "shut down non-production environments when not in use". On
Kubernetes, KEDA's cron scaler can scale workloads up during a time window and to zero outside it. Exclude only the
shared services that genuinely must stay up, and write down why.

## What makes the biggest difference

- **Auto-shutdown on notebooks,** which are the most commonly forgotten GPU users.
- **Visibility.** Put idle GPU-hours on the same report as spend; teams act on what they can see.
- **Sharing.** A shared pool or queue usually keeps GPUs busier than one machine per person.

## Common mistakes

- **Reserving big GPUs "just in case"** for work that runs once a week.
- **Keeping models loaded in memory permanently** for an internal tool used a few times a day.

See [hosting and data centres](/practice/hosting-and-data-centres/) and
[efficient training and inference](/practice/efficient-training-and-inference/).

## Sources

- [Serverless architecture for AI/ML workload processes](https://github.com/Green-Software-Foundation/patterns/blob/main/docs/architecture/system-topology/serverless-model-development.md), Green Software Foundation, Green Software Patterns (2025)
- [Use on-demand execution for AI and agent workloads](https://github.com/Green-Software-Foundation/patterns/blob/main/docs/architecture/system-topology/on-demand-execution-ai-agent-workloads.md), Green Software Foundation, Green Software Patterns (2025)
- [Reliability recommendations for sustainable workloads on Azure](https://learn.microsoft.com/en-us/azure/well-architected/sustainability/sustainability-reliability-recommendations), Microsoft Azure Well-Architected Framework (2026)
- [Cron scaler](https://keda.sh/docs/2.17/scalers/cron/), KEDA (CNCF) (2025)
