Slashdot Mirror

← Back to Stories (view on slashdot.org)

'Approximate Computing' Saves Energy

Posted by Soulskill on from the 1+1=3-for-sufficiently-large-values-of-1 dept.

hessian writes "According to a news release from Purdue University, 'Researchers are developing computers capable of "approximate computing" to perform calculations good enough for certain tasks that don't require perfect accuracy, potentially doubling efficiency and reducing energy consumption. "The need for approximate computing is driven by two factors: a fundamental shift in the nature of computing workloads, and the need for new sources of efficiency," said Anand Raghunathan, a Purdue Professor of Electrical and Computer Engineering, who has been working in the field for about five years. "Computers were first designed to be precise calculators that solved problems where they were expected to produce an exact numerical value. However, the demand for computing today is driven by very different applications. Mobile and embedded devices need to process richer media, and are getting smarter – understanding us, being more context-aware and having more natural user interfaces. ... The nature of these computations is different from the traditional computations where you need a precise answer."' What's interesting here is that this is how our brains work."

5 of 154 comments (clear)

  1. Numerical computation is pervasive by l2718 · · Score: 4, Informative

    This is not about data centers and databases. This is about scientific computation -- video and audio playback, physics simulation, and the like.

    The idea of doing a computation approximately first, and then refining the results only in the parts where more accuracy is useful is an old idea; one manifestation are multigrid algorithms.

  2. Fuzzy Logic anyone? by kbdd · · Score: 4, Informative
    Fuzzy logic was also supposed to save energy (in the form of requiring less advanced processors) by replacing computation intensive closed loop systems with table driven approximate logic.

    While the concept was interesting, it did not really catch up. Progress of silicon devices made it simply unnecessary. It ended up being used as a buzz word for a few years and quietly died away.

    I wonder if this is going to follow the same trend.

  3. Re:meanwhile... by ron_ivi · · Score: 4, Informative

    The majority of CPU cycles in data centers is going to be looking up and filtering specific records in database

    Approximate Computing is especially interesting in databases. One of the coolest projects in this space is Berkeley AMPLab's BlinkDB. Their cannonical example

    SELECT avg(sessionTime) FROM Table WHERE city='San Francisco' ERROR 0.1 CONFIDENCE 95%

    should give you a good idea of how/why it's useful.

    Their bencmarks show that Approximate Computing to 1% error is about 100X faster than Hive on Hadoop.

  4. Re:meanwhile... by ron_ivi · · Score: 4, Informative
    Better - more technical link/paper that explains it in more detail: http://www.cs.berkeley.edu/~sameerag/blinkdb_eurosys13.pdf

    DB: Queries with Bounded Errors and Bounded Response Times on Very Large Data

  5. Clive SInclair did this in 1974. by hamster_nz · · Score: 4, Informative

    Due to ROM and cost limitations the original Sinclair Scientific calulator only produced approximate answers, maybe to 3 or four digits.
    This was far more accurate than the answers given by a slide rule....

    For more info have a look at this page Reversing Sinclair's amazing 1974 calculator hack - half the ROM of the HP-35