Guidelines on Energy effecient code

Thanks for the upvote, jensbauer! Power efficient programming is a tricky area and it is not widely understood in the industry. It deserves a lot more attention than it gets.

For any who are interested in face-to-face events (a great way to pick up best practice and share experiences), my next engagements are Trondheim Developer Conference in October (here), the ARM Technical Symposium in Bangalore (also in October, here) and then at ARM TechCon in Santa Clara in November (here). Would be great to be able to meet up with any of the community who can attend any of those events. Do let me know if any of you have plans to attend.

Chris

Thanks for the upvote, jensbauer! Power efficient programming is a tricky area and it is not widely understood in the industry. It deserves a lot more attention than it gets.

For any who are interested in face-to-face events (a great way to pick up best practice and share experiences), my next engagements are Trondheim Developer Conference in October (here), the ARM Technical Symposium in Bangalore (also in October, here) and then at ARM TechCon in Santa Clara in November (here). Would be great to be able to meet up with any of the community who can attend any of those events. Do let me know if any of you have plans to attend.

Chris

pravinchanm: It's important to get the foundation right as the very first thing, thus if following Chris' documents, you'll cover the largest area of energy saving.

When you're sure you've absorbed and implemented your code the way Chris explains, and you still need to save further energy, it's time to consult the chip vendor's documents on the subject.

Chris: I really wish I could go to Trondheim; the Memory Access Ordering sounds like it's just for me. I get the impression that it will touch the Cortex-M7 too.

pravinchanm: This topic reminds me that it's important to also optimize your data if you can. Arrange your data in memory, so fetching, using and storing them will cost as little CPU cycles as possible. You know, optimizing isn't all about optimizing code, but it's also about optimizing your data by arranging them correctly, even swapping bits if possible/necesasry.

> Chris: I really wish I could go to Trondheim; the Memory Access Ordering sounds like it's just for me...

>

> techguyz: This topic reminds me that it's important to also optimize your data if you can...

Right. It's overlooked. Nowadays, I don't care to defragment my hard disks.

In tightly constrained systems, where ARM is commonly found, the arrangement of data could bring striking impact to various facets of performance.