[peerst]

This is a eval board, which is optimized for developer time.

In practice low power and performance are interchangeable (you try to race as fast as you can to the next point where you sleep as deep as you can). The CPU has decent sleep modes so when the system idles it can be made considerably low power.

So since Erlang is a language running on a VM you give up some sequential performance (power consumption). But in real world embedded systems you see a similar effect than with Erlang on the server: it reacts quite quickly on external events which is what most embedded systems do most of the time.

So the same which can be achieved on a server counterintuitively more performance you would expect looking at the sequential Erlang performance one can get in a embedded system. And this can be translated to power consumption directly and indirectly: quick reaction then sleep longer, possible reduction of clock speed or smaller CPU.

[keithnz]

where I am ( www.outpostcentral.com ) we look for extremely low power, so we have micros dedicated to that. Most sleep currents of processors like this are just too high for frequent battery operation. However we do use a higher power ARM processor for comms / high level processing functions, but that gets completely turned off for the majority of the time.

So this is still really cool, conceptually, this brings a very good platform to probably the lowest level that's practical. I've put it on the list of things to consider for one of our new product designs.