- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
LLMSpace estimates the carbon footprint of running LLM inference on low Earth orbit satellites, including emissions from hardware, launch, solar panels, batteries, and cooling. It compares orbital and terrestrial computing and studies how assumptions about launch emissions, hardware, lifetime, and workload affect the results.
Critical strengths
- LLMSpace brings several carbon sources into one analysis, including power and cooling equipment that simpler models did not consider.
- The paper acknowledges its uncertain assumptions and shows that changing them can reverse the comparison between orbital and terrestrial computing.
Critical weaknesses
- The connection to LLMs is weak. LLM experiments mostly show familiar effects of batching, throughput, and utilization without clearly leading to new insights about orbital computing. The main findings follow from general carbon accounting.
Questions for authors
-
Which findings actually depend on LLM behavior? If you replaced the LLM experiments with a generic workload described by power, throughput, and utilization, what important insight would be lost?
-
How do the LLM experiments change the satellite design or deployment decision? Can you show a case where prompt length, output length, or batching changes the preferred satellite configuration or whether orbital computing is worthwhile?
-
When would orbital inference be preferable to low-carbon computing on Earth? Your low-carbon terrestrial scenario performs best. Can you identify a realistic situation where space offers a benefit while meeting the same workload, response-time, and availability requirements?
Thank you for asking which design decisions change when we model the LLM explicitly.
Q1. What depends on LLM behavior? The launch accounting and basic utilization effects apply to many workloads. An average power and throughput profile can reproduce carbon for a fixed deployment. It loses the ability to predict how a different prompt and output mix changes the feasible batch size, memory requirement, and node count. Prompt tokens drive prefill and populate the key-value cache. Output tokens extend that cache and require sequential decode iterations. Batching can increase aggregate throughput while increasing queueing or changing per-request response times. We will distinguish time to first token, time per output token, and aggregate throughput and clarify that Equation 14 counts both input and generated tokens.
Q2. Can context length change the satellite choice? Yes, in an analytical memory-sizing example for the Qwen2.5-32B model. With a 16-bit key-value cache, each resident token takes 256 KiB. At batch 8, going from 4,096 to 32,768 resident tokens per sequence raises cache memory from 8 to 64 GiB. The long-context cache plus the model weights exceeds the commercial H100's 80 GB memory budget and fits within the B200's 180 GB budget. For 64 concurrently resident requests, independent replicas, and the evaluated batch sizes, the memory calculation gives one H100 node at short context and two H100 nodes at batch 4 or one B200 node at batch 8 at long context. Under Figure 3's one-node-per-platform inventory, the lower-carbon choice among these configurations switches from one H100 platform to one B200 platform. At long context, one B200 node has a modeled power budget of 30 kW versus 40 kW for two H100 nodes, with corresponding array, battery, and radiator requirements. The calculation assumes commercial-equivalent memory capacities and includes weights and cache. Flight latency and reliability require separate measurements. Figure 8 gives a second example. At the aggregate decode target of 250 output tokens/s, the model requires three A100 or two H100 GPU replicas, versus one B200.
Q3. When could orbit be preferable to low-carbon Earth? For the ground-originating inference evaluated in the paper, the 3 gCO₂e/kWh terrestrial case remains the lowest-carbon option within the modeled boundary. The submission establishes no orbital carbon advantage at matched response times and availability for that service. A plausible setting is generating a short event report from data already collected on an Earth-observation satellite, where raw data would otherwise have to be downlinked before the same report could be generated on Earth. ESA's Φsat-2 (https://www.esa.int/articles/introducing-phsat-2) illustrates how onboard processing can reduce downlink volume. For an LLM deployment, both placements would need the same input, report quality, delivery deadline, and on-time availability target. An orbital carbon advantage would require avoided downlink and terrestrial emissions to exceed the incremental onboard manufacturing, launch, and operating emissions, including any redundancy needed to meet the service target. Our current evaluation leaves that end-to-end comparison open.