Pierre-Yves Lapersonne@programming.dev to Programming@programming.devEnglish · 2 days agoRanking programming languages by energy efficiency (2021)www.sciencedirect.comexternal-linkmessage-square26fedilinkarrow-up160arrow-down19file-text
arrow-up151arrow-down1external-linkRanking programming languages by energy efficiency (2021)www.sciencedirect.comPierre-Yves Lapersonne@programming.dev to Programming@programming.devEnglish · 2 days agomessage-square26fedilinkfile-text
minus-squareFizzyOrange@programming.devlinkfedilinkarrow-up1·19 hours agoIt’s a very heavily gamed benchmark. The most frequent issues I’ve seen are: Different uses of multi-threading - some submissions use it, some don’t. Different algorithms for the same problem. Calling into C libraries to do the actual work. Lots of the Python submissions do this. They’ve finally started labelling stupid submissions with “contentious” labels at least, but not when this study was done.
minus-squareatzanteol@sh.itjust.workslinkfedilinkEnglisharrow-up2·14 hours agoThey provide the specific implementations used here: https://github.com/greensoftwarelab/Energy-Languages I dislike the “I thought of something that may be an issue therefore just dismiss all of the work without thinking” approach.
Why?
It’s a very heavily gamed benchmark. The most frequent issues I’ve seen are:
They’ve finally started labelling stupid submissions with “contentious” labels at least, but not when this study was done.
They provide the specific implementations used here: https://github.com/greensoftwarelab/Energy-Languages
I dislike the “I thought of something that may be an issue therefore just dismiss all of the work without thinking” approach.