Changes between Version 12 and Version 13 of CPUShare


Ignore:
Timestamp:
04/05/2008 02:29:14 PM (16 years ago)
Author:
Sam Hocevar
Comment:

reworded stuff

Legend:

Unmodified
Added
Removed
Modified
  • CPUShare

    v12 v13  
    11= Help libcaca research projects using CPUShare =
    22
    3 Image processing research sometimes requires expensive computations, for instance analysing the quality of an algorithm on thousands of different images. You can help the project by selling or donating your idle CPU cycles. We use the [http://www.cpushare.com/ CPUShare] project for this purpose: it provides all the infrastructure for reliable, secure and anonymous distributed computing.
     3Image processing research sometimes requires expensive computations, for instance analysing the quality of an algorithm on thousands of different images. You can help the project by selling or donating your idle CPU cycles. We use [http://www.cpushare.com/ CPUShare] for this purpose: it provides all the infrastructure for reliable, secure and anonymous distributed computing.
    44
    55== Getting started ==
     
    1111Then download our [/raw/CPUShare/libcaca-sell.cpu sell order] and put it in `/etc/cpushare/`. If your machine has several CPUs, you can place several copies of the same file in `/etc/cpushare/`, just make sure their names end in `.cpu`.
    1212
    13 Finally, simply run `/etc/init.d/cpushare start` and the CPUShare daemons will start.
     13Finally, start the CPUShare daemons:
     14{{{
     15/etc/init.d/cpushare start
     16}}}
    1417
    1518If you are not using Debian or Ubuntu, you can either try to install and run CPUShare from source (good luck!) or run this Live CD, either by burning and booting it, or by running it in an emulator (see more information [https://www.cpushare.com/wiki/cpushare/CPUShareLiveCD on the CPUShare wiki]):
    1619 * [/raw/CPUShare/libcaca-cpushare-livecd.iso libcaca-cpushare-livecd.iso] Live CD image (5.8 MB)
    1720
    18 == What happens exactly? ==
     21== How does it work? ==
    1922
    20 Your machine's idle CPU cycles will be available on the CPUShare platform. The CPUShare daemons run at a very low priority (`nice -19` by default) but you can stop them at any time if the impact on your system is too important.
     23Your machine's idle CPU cycles will be available to CPUShare users. There is no way to know whether your CPU will only be used for libcaca projects, but if you use our `.cpu` file, the CPUCoins earned by running other software will be credited to the libcaca project's account, too. We will in turn use these CPUCoins to buy CPU cycles on other machines; maybe yours, maybe not.
    2124
    22 There is no way to know whether your CPU will only be used for libcaca projects. However, because you use our `.cpu` file, the CPUCoins earned by running other software will be credited to the libcaca project's account, too. We will in turn use these CPUCoins to buy CPU cycles on other machines; maybe yours, maybe not.
     25The CPUShare daemons run at a very low priority (`nice -19` by default) but you can stop them at any time if the impact on your system is too important.
    2326
    2427If you do not like giving CPUCoins directly to the libcaca project, you can create your own `.cpu` file by creating an account on [http://www.cpushare.com/ cpushare.com] and [https://www.cpushare.com/orders/ creating a new sell order].