<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>EACOF: A Framework for Providing Energy Transparency to enable Energy-Aware Software Development · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1406.0117/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1406.0117/feed.xml" rel="self" type="application/rss+xml" /><item><title>EACOF: A Framework for Providing Energy Transparency to enable Energy-Aware Software Development — mentioned by hayfield</title><link>https://news.ycombinator.com/item?id=8236257</link><guid isPermaLink="false">urn:hackerpapers:mention:1406.0117:8236257</guid><pubDate>Thu, 28 Aug 2014 07:37:36 GMT</pubDate><description>&lt;p&gt;You can have an impact on power consumption at a range of levels. From choosing appropriate algorithms, to switching to different data types, to changing compiler flags. Add together a few of these &amp;#x27;easy&amp;#x27; 5-10% energy savings and you&amp;#x27;ve just reduced your application&amp;#x27;s energy consumption by a third (OK, it&amp;#x27;s not quite that simple, but the principle stands). A couple of citations: http://arxiv.org/pdf/1406.0117v1.pdf (algorithms / data types) http://arxiv.org/pdf/1303.6485.pdf (compiler flags)&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1406.0117/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.SE</category></item></channel></rss>
