Changes between Version 30 and Version 31 of CPUShare
- Timestamp:
- 09/28/2008 12:36:58 AM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CPUShare
v30 v31 1 = Help libcacaresearch projects with CPUShare =1 = Help Caca Labs research projects with CPUShare = 2 2 3 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 [http://www.cpushare.com/ CPUShare] for this purpose: it provides all the infrastructure for reliable, secure and anonymous distributed computing. … … 18 18 }}} 19 19 20 Then download our [/files/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`. Finally, start the CPUShare daemons:20 Then download our [/files/CPUShare/caca-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`. Finally, start the CPUShare daemons: 21 21 {{{ 22 22 % cd /etc/cpushare 23 % curl http:// libcaca.zoy.org/files/CPUShare/libcaca-sell.cpu -o libcaca-cpu0.cpu24 % cp libcaca-cpu0 libcaca-cpu1.cpu # optional, if you have two CPUs or two cores23 % curl http://caca.zoy.org/files/CPUShare/caca-sell.cpu -o caca-cpu0.cpu 24 % cp caca-cpu0 caca-cpu1.cpu # optional, if you have two CPUs or two cores 25 25 % /etc/init.d/cpushare start 26 26 }}} 27 27 28 28 If 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]): 29 * [/files/CPUShare/ libcaca-cpushare-livecd.iso libcaca-cpushare-livecd.iso] Live CD image (5.8 MB)29 * [/files/CPUShare/caca-cpushare-livecd.iso caca-cpushare-livecd.iso] Live CD image (5.8 MB) 30 30 31 31 The qemu emulator gives near native performance if you use the kqemu kernel module. Just run: 32 32 {{{ 33 % qemu -cdrom libcaca-cpushare-livecd.iso33 % qemu -cdrom caca-cpushare-livecd.iso 34 34 }}} 35 35 36 36 == How does it work? == 37 37 38 Your 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. We will in turn use these CPUCoins to buy CPU cycles on other machines; maybe yours, maybe not.38 Your 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 Caca Labs projects, but if you use our `.cpu` file, the CPUCoins earned by running other software will be credited to the Caca Labs account. We will in turn use these CPUCoins to buy CPU cycles on other machines; maybe yours, maybe not. 39 39 40 40 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. 41 41 42 If you do not like giving CPUCoins directly to the libcacaproject, 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].42 If you do not like giving CPUCoins directly to the Caca Labs 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]. 43 43 44 44 '''Note: we ''cannot'' use your data, only your CPU. CPUShare is secure and prevents malicious code from using any other resource.'''