4 ms·
"Costs more" in terms of energy per... what quantity exactly? Instruction executed? Clock cycle? Datum processed?
by mehrdadn 8y ago
"Costs more" in terms of energy per... what quantity exactly? Instruction executed? Clock cycle? Datum processed?
- dahart 8y agoIn the paper it’s energy per rendered pixel. You could translate that abstractly to watts per flop.
- deleted 8y ago[deleted]
- hermitdev 8y agoI think practically, for useful analysis in business it would be wattage per unit of useful work (or datum processed as you suggest). For instance, I work in finance, so what is the wattage per option price calculation?
- mehrdadn 8y agoThe reason I asked was that it wasn't clear to me if the parent comment was measuring the same way or not re: memory accesses. It seemed pretty expected that a memory access would be more expensive per byte (it takes like hundreds of clock cycles...) but it wasn't obvious to me if it would be so per clock so I wanted to clarify which was meant.
- hermitdev 8y agoI absolutely agree that it wasn't clear. I don't think wattage per clock cycle is a meaningful measure here - after all, all languages will have the same wattage per clock cycle, if they're executing the same instructions. What's important is wattage per unit of useful end product, in my example pricing an option. For others, it might be wattage per web page served or anything else.
- deepnotderp 8y agoEnergy per operation and delay per operation, on the order of ~40-100X more than compute...