Your app might run cheaper and leaner on ARM. Many workloads stay on the same kind of processor out of habit. Yet cloud providers offer ARM-based machines too. Many of them do more work for each watt. But how well they do differs from program to program. The only way to know for your code is to measure it. Here is the fix you can use today. First, build container images for more than one kind of processor, following Docker's build guide. Next, test a typical service on an ARM machine. Compare throughput, response time, cost and energy, using tools like Cloud Carbon Footprint. Then move the services where the numbers are better. The Green Software Foundation suggests testing your software on other kinds of processor. GreenCode draws on these patterns when it checks software. GreenCode helps tackle this by mapping your running systems and rebuilding them as code. It shows which services use the energy, including ones barely running at all. That was GreenCode Tech Tip number fifty-three. Follow for the next tip, and find more on greencode.ai/tech-tips.