Again I like to throw in some other point of view into the discussion.
As
exemplary (!) for sure it is to watch energy consumption, measure things, snoop for energy devourers, keep the footprint small, and also to point out FreeBSD's powermanagment could do better - no question - don't oversee to put the numbers in perspective to each other.
If I understood right we are talking here some desktop machine, right?
Let's assume there is some >=4-core CPU @ >=2.7GHz, maybe some nice 3D graphics adapter, most likely WLAN, maybe wireless keyboard, wireless mouse, maybe some Bluetooth device in use, maybe a switch, for sure at least a router, and one monitor... so, we are talking here about 3W within a system with an overall consumption of at least 150W at running idle.
Don't get me wrong.
kimminss0, you found that difference, and were absolutely right to ask for its source. That is right, and for sure a good thing. Out of question. Good engineering!
But as long as we're not talking some embedded, battery driven system where really every single W counts, and so the whole system would have been specified by scratch by complete other specifications, I think this discussion is more academic, then to really find actual potential for energy savings. (Well, if there was potential to improve FreeBSD's powermanagement... - looking at the sum of all machines, that really was a large cake. But that's not the point here so far.)
Maybe I'm completely mistaken (again), and
kimminss0 already squeezes every single watt that can be spared. But if not, you could easily save app. 20W by just using wires instead of wireless, which mostly aims at WLAN, and bluetooth (since most users use such I simply insinuated that was the case for to bring an example.)
All I'm saying is:
If so, I'd like to purchase them.
Watch out not to lose yourself counting beans at the wrong edge, while there could be found way more saving potential at other places.