Skip to main content

Operations

Runtime and infrastructure patterns for optimising resource utilisation and minimising operational emissions.

13 patterns
Delete or auto-expire unused storage

Storage that is no longer used still occupies hardware and carries embodied carbon. Deleting unused storage, either manually or through automated retention policies, reduces the hardware needed to hold data, provided deletion is controlled so that data still needed is not lost.

  • data-lifecycle
  • size:small
  • storage
Match CPU capacity to average and peak utilization

Provisioned CPU capacity has to cover peak demand, so the gap between average and peak utilization determines how much hardware sits idle. Matching CPU capacity to both average and peak utilization reduces idle resources while protecting performance at peak load.

  • compute
  • monitoring
  • size:medium
Optimise storage utilization

It's better to maximise storage utilisation so the storage layer is optimised for the task, not only in terms of energy proportionality but also in terms of embodied carbon. Two storage units running at low utilization rates will consume more energy than one running at a high utilization rate. In addition, the unused capacity on the underutilised storage unit could be more efficiently used for another task or process.

  • size:small
  • storage
Optimize power consumption for edge AI inference

Edge AI inference workloads consume significant power on resource-constrained devices. Optimizing power-performance characteristics through dynamic workload scheduling, thermal-aware throttling, and battery-level policies reduces energy consumption and extends battery life while maintaining acceptable accuracy and latency.

  • ai
  • edge-computing
  • energy-efficiency
  • inference
  • machine-learning
  • size:medium
Remove unused assets

Unused cloud resources such as databases, storage buckets, and compute instances continue to consume energy and generate embodied carbon; identifying and decommissioning them eliminates unnecessary waste.

  • cloud
  • size:small
Rightsize compute to match utilization

Compute capacity that is provisioned well above what a workload actually uses wastes energy and embodied carbon. Rightsizing matches allocated compute to measured utilization, either by resizing a VM's resources or by moving to a better-fitting pre-configured instance type.

  • compute
  • monitoring
  • size:small
Scale down applications when not in use

Applications consume CPU even when they are not actively in use. For example, background timers, garbage collection, health checks, etc. Even when the application is shut down, the underlying hardware is consuming idle power.

  • cloud
  • size:small
Scale down kubernetes applications when not in use

In order to reduce carbon emissions and costs, Dev&Test Kubernetes clusters can turn off nodes out of office hours. Thereby, optimization is implemented at the cluster level. For production clusters, where nodes need to stay up and running, optimization needs to be implemented at the application level.

  • kubernetes
  • size:small
Scale infrastructure with user load

Demand for resources depends on user load at any given time. However, most applications run without taking this into consideration. As a result,resources are underused and inefficient.

  • cloud
  • compute
  • size:medium
Scale Kubernetes workloads based on relevant demand metrics

By default, Kubernetes scales workloads based on CPU and RAM utilization. In practice, however, it's difficult to correlate your application's demand drivers with CPU and RAM utilization. Scaling your workload based on relevant demand metrics that drive scaling of your applications, such as HTTP requests, queue length, and cloud alerting events can help reduce resource utilization, and therefore also your carbon emissions.

  • cloud
  • kubernetes
  • role:cloud-engineer
  • role:software-engineer
  • serverless
  • size:medium
Time-shift Kubernetes cron jobs

The carbon emissions of a software system depends on the power consumed by that software, but also on the Carbon intensity of the electricity it is powered on. For this reason, running energy-efficient software on carbon intensive electricity grid, might be inefficient to reduce its global carbon emissions. Carbon aware time scheduling, is about scheduling workloads to execute, when electricity carbon intensity is low.

  • kubernetes
  • size:medium
Use carbon-aware scheduling and region selection for AI workloads

Reduce the carbon impact of AI workloads by running them in cloud regions with lower grid carbon intensity and scheduling deferrable jobs during periods of high renewable energy availability.

  • ai
  • cloud
  • compute
  • machine-learning
  • size:large
Use circuit breaker patterns

Modern applications need to communicate with other applications on a regular basis. Since these other applications have their own deployment schedule, downtimes and availability, the network connection to these application might have problems. If the other application is not reachable, all network requests against this other application will fail and future network requests are futile.

  • compute
  • size:medium