• State Not Answered
  • Locked Locked
  • Replies 11 replies
  • Subscribers 20 subscribers
  • Views 8539 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Guidelines on Energy effecient code

techguyz

Hi Experts,

The well optimized hardware functionality could be messed up by the poor software programming.

Is there any general guidelines recommended by ARM on the power optimized programming ?

Regards,

Techguyz

Parents
  • 0

    For application software just optimize for performance - as a first order approximation faster code is generally more energy efficient (and there are LOTS of tools to help writing fast code).

    That should include looking at techniques such as multi-threading - running 4 parallel threads at a slower clock speed on 4 "LITTLE" cores may be a lot more efficient than running one thread at a high clock speed on a "big" core. Higher frequencies need higher voltages, and energy per FLOP/IOP is proportional to V squared, so even in a system without big.LITTLE this advice applies, big.LITTLE just amplifies the effect.

    HTH,
    Pete

Reply
  • 0

    For application software just optimize for performance - as a first order approximation faster code is generally more energy efficient (and there are LOTS of tools to help writing fast code).

    That should include looking at techniques such as multi-threading - running 4 parallel threads at a slower clock speed on 4 "LITTLE" cores may be a lot more efficient than running one thread at a high clock speed on a "big" core. Higher frequencies need higher voltages, and energy per FLOP/IOP is proportional to V squared, so even in a system without big.LITTLE this advice applies, big.LITTLE just amplifies the effect.

    HTH,
    Pete

Children
No data