The Green Shift: Transitioning .NET Services Across Architectures
summary
Practical checklist and real numbers for moving .NET services to ARM: expect 1.57 requests per watt in Cloudflare‑style tests and vendor reports of 37–47% price‑performance improvements and ~20% boosts on some Cobalt instances. Build with AnyCPU so managed assemblies run anywhere, install .NET on an ARM runtime, add one ARM test runner in CI, handle native libs by recompiling or replacing, use Chemo cross‑compile or self‑hosted ARM runners, avoid long‑term emulation for best performance.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:28What makes software green?
- 6:00Energy efficiency
- 8:09CPU: RISC vs. CISC
- 11:36Why should you change?
- 13:49The green wins
- 17:46Hardware efficiency
- 24:49The migration journey
- 42:01Takeaways
- 42:27Outro
related talks
06mChange Your Architecture and Save the World
29mGitOps Sustainability with Flux and arm64
20mHigh-Performance Computing that’s Earth Friendly
16mGreen Code: Transforming DevOps for a Sustainable Future
58mBuilding a green supercomputer in the cloud
37mRock Your Code Code and App Performance for Microsoft .Net
29mThe Progress for Cloud Computing on Arm architecture
10mEnergy-Efficient and Cost-Optimized Serverless Computing