---
title: Carbon-Aware Temporal Shifting
url: https://www.emergentmind.com/topics/carbon-aware-temporal-shifting
type: topic
---

# Carbon-Aware Temporal Shifting

Searching arXiv for recent and foundational papers on carbon-aware temporal shifting and adjacent scheduling settings.
Carbon-aware temporal shifting is the practice of deferring or advancing delay-tolerant computation or data movement so that execution occurs when electricity carbon intensity is lower, thereby reducing associated emissions without reducing total energy use. In the literature, the concept appears as time-flexible cloud scheduling, day-ahead datacenter load shaping, pause-and-resume execution, slack-aware federated training, transfer scheduling, and workflow interruption, all of which use time-varying grid signals such as average carbon intensity, marginal carbon intensity, or nodal carbon intensity to align energy use with lower-carbon periods [2110.13234], [2106.11750], [2509.08980], [2406.09650], [2607.03324].

## 1. Definition, scope, and relation to adjacent strategies

Temporal shifting uses execution-time flexibility rather than geographic relocation. In the cloud setting, it exploits release times, deadlines, and interruptibility to align energy consumption with periods of lower grid carbon intensity \(CI(t)\), measured in \(gCO_2/kWh\) or \(kgCO_2e/kWh\) depending on the study. This differs from geo-shifting, which migrates work across regions to exploit spatial carbon differences, and from demand response optimized for electricity prices or grid stability rather than emissions [2110.13234], [2306.06502].

The distinction is operationally important. Temporal shifting avoids inter-region data movement, latency penalties, compliance issues, and dependence on transcontinental availability zones, whereas geo-shifting can achieve larger reductions when low-carbon regions are available but may incur network emissions and migration overheads [2110.13234], [2504.14022]. In network-intensive settings, temporal shifting also applies to data transfers: the same source–destination path can have materially different emissions at different times because the sender, receiver, and intermediate network segments are supplied by grids with changing carbon intensity [2406.09650].

The scope of the topic has broadened well beyond batch cloud jobs. Recent work treats temporal shifting as a general mechanism for federated learning rounds with slack time, scientific workflow interruption and resumption, inter-datacenter transfer scheduling, GPU scheduling for clinical AI, and AI data center control under distribution-system carbon signals [2509.08980], [2508.14625], [2506.04117], [2606.01766], [2607.03324]. This suggests that the central abstraction is not a specific scheduler, but a workload with admissible temporal slack and an external carbon signal of sufficient temporal variability.

## 2. Carbon signals, workload flexibility, and emissions accounting

The basic signal is the time-varying carbon intensity of electricity. In one widely used cloud formulation, emissions are computed as
\[
E = \sum_t \mathrm{Energy}(t)\cdot CI(t),
\]
or, for job \(i\),
\[
E_i = \sum_t x_{i,t}\, e_i(t)\, CI(t),
\]
with \(x_{i,t}\in\{0,1\}\) denoting assignment decisions [2110.13234]. Scientific workflow studies use the equivalent discrete form
\[
C = \sum_t CI_t P_t \Delta t,
\]
and distinguish average carbon intensity from marginal carbon intensity, the latter representing emissions attributable to incremental demand [2503.13705], [2508.14625]. In power-distribution-aware AI data center control, the signal becomes nodal carbon intensity \(w_{i,t}\), derived from a carbon emission flow model coupled to distribution-system power flow rather than from a regional average alone [2607.03324].

Workload flexibility is characterized by three recurring attributes. The first is the time window: jobs may have a release time \(r_i\), a deadline \(D_i\), or a slack horizon \(t_{sl}\). The second is execution structure: some jobs are non-interruptible and must occupy one contiguous interval, whereas others can be checkpointed, chunked, or resumed across multiple low-carbon slots. The third is issuance pattern: ad hoc jobs can usually only be deferred into the future, while scheduled jobs can often be moved earlier or later within a window [2110.13234], [2509.08980].

The same abstractions recur across domains. In federated learning, each client must complete \(T\) local rounds within an extended horizon \(T+t_{sl}\), and permissible slots are chosen from the \(T\) lowest-carbon positions in that horizon [2509.08980]. In scientific workflows, tasks are atomic, but workflow-level pause and resume is feasible because intermediate data are persisted; interrupted scheduling therefore acts between task windows rather than within individual tasks [2508.14625]. In data movement, the flexible object is not CPU time but bytes transferred over a deadline-constrained interval, optionally split across several low-carbon windows [2406.09650], [2506.04117].

## 3. Scheduling formulations and algorithmic patterns

A canonical continuous objective minimizes time-integrated emissions:
\[
\min \sum_i \int_{s_i}^{s_i+d_i} p_i \, CI(t)\, dt,
\]
while a discrete cloud formulation minimizes
\[
\min \sum_t \left(CI(t)\sum_i x_{i,t} e_i(t)\right)
\]
subject to capacity, time-window, and continuity constraints [2110.13234]. From this common core, the literature develops several scheduler families.

One family uses direct slot selection within a deadline window. Examples include greedy lowest-\(CI\)-first placement for nightly jobs, contiguous-interval heuristics for non-interruptible jobs, and chunk-based heuristics for interruptible jobs [2110.13234]. A related online formulation is the pause-and-resume problem, where a workload must accept exactly \(k\) slots by deadline \(T\), carbon intensity is revealed sequentially, and switching between run and pause incurs cost \(\beta\). The proposed double-threshold algorithms are optimal among deterministic online algorithms for both the minimization and maximization variants under bounded inputs [2303.17551].

A second family performs aggregate capacity shaping rather than per-job scheduling. Google’s Carbon-Intelligent Compute Management computes day-ahead Virtual Capacity Curves (VCCs), hourly caps on flexible reservations that preserve overall daily capacity while suppressing flexible execution in forecasted high-carbon hours [2106.11750]. In this model, higher-tier interactive services remain unaffected, and flexible throughput is protected through risk-inflated daily targets and chance constraints on power capping.

A third family integrates temporal shifting with workload-specific structure. In federated learning, a scheduler jointly chooses client participation and slot assignment under a carbon budget using an \(\alpha\)-fair objective, then corrects selection bias with U-FedAvg and mitigates temporal imbalance through a final full-participation fine-tuning phase [2509.08980]. In precedence-constrained data processing, \(\texttt{PCAPS}\) uses a threshold \(\Psi_\gamma\) that combines carbon intensity with precedence-driven task importance, ensuring that bottleneck tasks continue to run even in high-carbon periods while low-importance tasks are deferred [2502.09717]. In inter-datacenter transfers, LinTS formulates slot-level throughput allocation as a linear program and then maps throughput decisions to thread counts using a throughput–threads model [2506.04117].

These formulations differ in decision granularity—start times, slot assignments, throughput rates, aggregate capacity caps, or pause/resume states—but they all operationalize the same principle: emissions are reduced when flexible demand is moved from higher-carbon to lower-carbon intervals, subject to workload and infrastructure constraints.

## 4. Empirical behavior across application domains

Reported benefits depend strongly on regional carbon-intensity variability, slack length, interruptibility, and forecast quality. In a simulation over Germany, Great Britain, France, and California in 2020, nightly non-interruptible 30-minute jobs achieved about \(11.2\%\) savings in Germany and about \(33.7\%\) savings in California with \(\pm 8\)-hour windows and \(5\%\) forecast error, while a StyleGAN2-ADA-inspired machine learning workload achieved about \(13.3\%\) to \(18.9\%\) reductions under a semi-weekly interrupting strategy [2110.13234].

| Domain | Setting | Reported outcome |
|---|---|---|
| Cloud workloads | Nightly jobs and a machine learning project | \(\pm 8\)-hour nightly shifting yielded about \(33.7\%\) savings in California; semi-weekly interrupting scheduling yielded about \(13.3\%\)–\(18.9\%\) reductions [2110.13234] |
| Federated learning | Slack-aware client and time-slot scheduling | With \(t_{sl}=236\) hours, clients with high CI variability saw up to \(\sim 60\%\) emission reduction; \(80\%\) of clients reduced at least \(10\%\) [2509.08980] |
| Inter-datacenter transfers | LinTS scheduling over 72 hours | Up to \(66.1\%\) lower emissions versus the worst case and up to \(15.4\%\) lower emissions versus FCFS while meeting all deadlines [2506.04117] |
| Scientific workflows | Seven Nextflow workflows | Temporal shifting was capable of decreasing emissions by over \(80\%\), and resource scaling capable of decreasing emissions by \(67\%\) [2508.14625] |
| Clinical AI GPU workloads | Night-window batching versus CUCA\(_{0.45}\) | The overnight rule closed about \(78\%\) of the average \(kg\ CO_2e\) gap from urgency-only to CUCA\(_{0.45}\); CarbonShift let about \(46\%\) of the most urgent jobs miss their deadline [2606.01766] |

Operational deployments and system-level studies show more moderate but still material effects. In Google’s datacenter system, some clusters saw roughly \(50\%\) reductions in flexible load during peak-carbon hours, corresponding to about \(8\%\) power reductions in those hours, while a controlled campus experiment found about \(1\%\)–\(2\%\) average power reduction during the highest-carbon hours on shaped days [2106.11750]. For network-intensive data movement, hourly path-average carbon intensity on a UC→TACC path ranged from \(255.714\) to \(488.6\) over 51 hours, indicating nearly \(2\times\) variation solely due to time-of-day and day-to-day grid conditions [2406.09650].

The literature therefore does not support a single magnitude claim. Instead, it documents a spectrum ranging from a few percent in low-variability grids or tight windows to much larger reductions when slack is long, interruption is feasible, or the underlying carbon signal has strong diurnal or weekly structure.

## 5. Uncertainty, practical limits, and recurring trade-offs

Temporal shifting is fundamentally limited by forecast quality, workload structure, and the carbon variability of the underlying grid. In the cloud experiments over 2020, the measured mean absolute error for National Grid ESO’s 48-hour carbon-intensity forecasts was about \(10\ gCO_2/kWh\), roughly \(5\%\) of the annual mean, and simulated forecast noise reduced gains more strongly for interrupting strategies than for non-interrupting contiguous scheduling [2110.13234]. More explicitly uncertainty-aware work shows that point forecasts can mis-rank cleaner and dirtier days; conformal prediction intervals achieved target coverages close to \(92\%\), \(96\%\), and \(99\%\) across several regions and prevented a \(5\%\) increase in emissions in a temporal-shifting case study and a \(14\%\) increase in a spatial case study for a 20 MW datacenter cluster [2407.02390].

Upper-bound analyses indicate that ideal and practical outcomes differ sharply. Across 123 regions, temporal-only scheduling with perfect foresight and one-year slack achieved a global average reduction of about \(135\ gCO_2e\), or about \(37\%\) of the global mean CI, but with practical 24-hour slack the average temporal reduction fell to about \(31\)–\(32\ gCO_2e\), or about \(8.4\%\) of the global average. The same study argues that simple policies often yield most of these reductions and that the relative benefit of carbon-aware scheduling decreases as the energy supply becomes greener [2306.06502].

A second recurring trade-off is that carbon minimization may conflict with other objectives. In clinical AI, carbon-first stress-test policies such as CarbonGreedy and CarbonShift produced low average \(kg\ CO_2e\) but disrupted urgent scheduling, with CarbonShift allowing about \(46\%\) of critical jobs to miss their deadlines in the simulator [2606.01766]. In WAN-aware geo-shifting, ignoring network emissions can reverse an apparently favorable migration decision: for network-heavy jobs, WAN carbon can exceed compute by \(5\times\), and traceroute-only methods can underestimate path carbon by \(2\)–\(3\times\) [2504.14022]. More generally, temporal shifting improves carbon outcomes less than spatial shifting in some cloud studies, and when both are combined the incremental benefit of temporal adjustment is often positive but smaller than the spatial effect [2512.08725].

These results caution against treating temporal shifting as a universally dominant control lever. Its effectiveness is contingent rather than absolute.

## 6. Deployment patterns and research directions

Operational guidance in the literature is comparatively consistent. Suitable workloads include short-running batch jobs, CI/CD, backups, ETL, periodic analytics, simulations, ML training and sweeps, reporting pipelines, and other jobs with explicit deadlines, known durations, and checkpointability [2110.13234]. Production integration typically starts by attaching metadata such as release time, deadline, duration, and interruptibility to jobs, then extending schedulers or controllers to consume carbon forecasts. Concrete examples include Slurm and HTCondor extensions, Kubernetes CronJobs with flexible execution windows, carbon-aware queue delays for serverless systems, and scheduler-agnostic admission control through hourly capacity caps [2110.13234], [2106.11750].

Current research directions broaden the objective beyond operational carbon. One strand couples temporal shifting with 24/7 carbon-free energy procurement, modeling daily conservation windows and inter-site virtual links; in that setting, the costs of 24/7 CFE are reduced by \(1.29\pm0.07\) EUR/MWh for every additional percentage of flexible load [2405.00036]. Another strand co-optimizes carbon with water and land-use footprints, finding that temporal shifting also decreases those footprints, though to a lesser extent than spatial shifting [2512.08725]. Reliability-aware formulations add embodied carbon and server lifetime degradation, achieving up to \(21\%\) total carbon reduction in a heterogeneous data-center model that jointly schedules batch deferral, interactive migration, and backup allocation [2504.00518].

Future work in the cited literature repeatedly returns to the same themes: multi-objective optimization over cost, peak power, and emissions; integration of temporal and spatial shifting; improved average and marginal carbon forecasting; explicit modeling of correlated forecast errors; production-grade middleware for declarative time flexibility and checkpointing; and fairness controls to prevent systematic deferral of the same jobs or tenants [2110.13234], [2509.08980], [2407.02390], [2506.04117]. A plausible implication is that the mature form of carbon-aware temporal shifting will be neither a standalone heuristic nor a single optimization routine, but a scheduler interface that exposes temporal flexibility, forecast uncertainty, and system priorities as first-class control variables.

Source: https://www.emergentmind.com/topics/carbon-aware-temporal-shifting