Papers › The Ecological Impact of High-performance Computing in Astrophysics
The Ecological Impact of High-performance Computing in Astrophysics
Simon Portegies Zwart
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
The importance of computing in astronomy continues to increase, and so is its impact on the environment. When analyzing data or performing simulations, most researchers raise concerns about the time to reach a solution rather than its impact on the environment. Luckily, a reduced time-to-solution due to faster hardware or optimizations in the software generally also leads to a smaller carbon footprint. This is not the case when the reduced wall-clock time is achieved by overclocking the processor, or when using supercomputers. The increase in the popularity of interpreted scripting languages, and the general availability of high-performance workstations form a considerable threat to the environment. A similar concern can be raised about the trend of running single-core instead of adopting efficient many-core programming paradigms. In astronomy, computing is among the top producers of green-house gasses, surpassing telescope operations. Here I hope to raise the awareness of the environmental impact of running non-optimized code on overpowered computer hardware.
Code
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
Not run by Syntology. Nothing on this page verifies that the listed code works.
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections