bkil vs. programming

= The Computer Language Benchmarks Game The Computer Language Benchmarks Game is a free software project for comparing how a given subset of simple algorithms can be implemented in various popular programming languages. The project consists of: * A set of very simple algorithmic problems * Various implementations to the above problems in various programming languages * A set of unit tests to verify that the submitted implementations solve the problem statement * A framework for running and timing the implementations * A website to facilitate the interactive comparison of the results = Supported languages Due to resource constraints, only a small subset of common programming languages are supported, up to the discretion of the game's operator. https://benchmarksgame.alioth.debian.org/ * Ada * C * Chapel * Clojure * C# * C++ * Dart * Erlang * F# * Fortran * Go * Hack * Haskell * Java * JavaScript * Lisp * Lua * OCaml * Pascal * Perl * PHP * Python ...

How come so few donate their free resources to volunteer computing projects ? Depending on the exact computer configuration, the difference in system power consumption between using and near-idling the CPU (~35W-80W) or GPU (~30W-100W) can be reasonably small . The difference is usually smaller than the difference between a power efficient (25-60W) and a basic system (100-200W). Hence in my view, it usually worths it to put your free resources to use in some way if your daily work does not strain your machine continuously at 100%. There's an a project of special interest that has similar aim to what I have invented earlier: It is special in that any participant can freely use the communal grid for their own purposes . Prioritization is fair - it is based on previous record of contribution. This type of project is also useful for the selfish kind, as if you think it over, you can eventually get back the contributed CPU time and energy, but at a much faster pace. It would stil...

I have added format "48000:16:2" to the audio_output section and samplerate_converter 4 to the main body of ~/.mpdconf . This has reduced mpd's CPU usage from 30-40% to less than 5%! I should have done this before. I found out about this issue by doing web searches, but I have later encountered the neatly written summary linked below. In short: good quality (double?) software scaling is not very economical. http://mpd.wikia.com/wiki/Tuning