| | 1 | = Computing with BOINC = |
| | 2 | |
| | 3 | BOINC is a platform for distributed "high throughput computing", |
| | 4 | i.e. large numbers of independent compute-intensive jobs, |
| | 5 | where there performance goal is high rate of job completion |
| | 6 | rather than low turnaround time of individual jobs. |
| | 7 | It also offers low-level mechanisms for distributed data storage. |
| | 8 | |
| | 9 | BOINC has a client/server architecture. |
| | 10 | The server distributes jobs. |
| | 11 | The client runs on worker nodes, which execute jobs. |
| | 12 | |
| | 13 | BOINC was originally designed for "volunteer computing", |
| | 14 | where the worker nodes are consumer devices (desktop and laptop computers, |
| | 15 | tables, smartphones) volunteered by their owners. |
| | 16 | It addresses the various challenges inherent in this environment |
| | 17 | (heterogeneity, host churn and unreliability, scale, security, and so on). |
| | 18 | |
| | 19 | In this arena, there are many servers, operated by various "BOINC projects" |
| | 20 | such as SETI@home, LHC@home, IBM World Community Grid, and so on. |
| | 21 | The BOINC client can be "attached" to one or many of these; |
| | 22 | it processes jobs for the projects to which it is attached. |
| | 23 | |
| | 24 | BOINC can also be used for in-house computing within an organization (e.g. a company). |
| | 25 | In this case case the worker nodes would be |
| | 26 | are cluster nodes or other organizational computers, |
| | 27 | and they would be attached to the organization's server. |
| | 28 | |
| | 29 | BOINC is distributed under the LGPL v3 open-source license. |
| | 30 | It can be used for any purpose (academic, commercial, or private) |
| | 31 | and can be used with applications that are not open-source. |
| | 32 | |
| | 33 | == Getting started == |
| | 34 | |
| | 35 | To compute using BOINC, you will need to set up a BOINC server |
| | 36 | and configure your applications to run under BOINC. |
| | 37 | Instructions for doing this are [ProjectMain here]. |
| | 38 | |
| | 39 | If you're doing in-house computing, |
| | 40 | install the BOINC client on your computers, and you're done. |
| | 41 | We won't discuss this case further. |
| | 42 | |
| | 43 | Next, you'll need to get clients to attach to your server. |
| | 44 | There are several ways to do this: |
| | 45 | |
| | 46 | 1. Create a public-facing web site for your project. |
| | 47 | Announce it and publicize it in whatever channels are available to you: |
| | 48 | mass media, social media, newletters, paid advertising, etc. |
| | 49 | |
| | 50 | 1. Contact [ProjectPersonnel David Anderson] and ask to have your project listed by BOINC. |
| | 51 | You'll need to convince me that a) your project is doing |
| | 52 | what you claim it is, and b) you're following a set of security practices. |
| | 53 | Your project will then a) be announced on the BOINC web site news column, |
| | 54 | b) listed on the BOINC web site, and |
| | 55 | c) appear in the list of projects shown in the BOINC client GUI. |
| | 56 | |
| | 57 | 1. Contact [ProjectPersonnel David Anderson] and ask to have your project |
| | 58 | listed in [https://scienceunited.org Science United]. |
| | 59 | You'll need to tell me what type of research your project is doing, |
| | 60 | and then you'll automatically get computing power from volunteers |
| | 61 | who have registered an interest in that area. |
| | 62 | This has the advantage that you don't have to create a public-facing web site or do any publicity. |
| | 63 | In addition, you can ask to be listed in Science United even before you've created your project. |
| | 64 | At that point I can tell roughly how much computer power you'll get, |
| | 65 | and you can decide whether this justified the investment in creating a project. |
| | 66 | |
| | 67 | These approaches are not mutually exclusive; you can do any or all of them. |
| | 68 | |
| | 69 | == Organizational structures == |
| | 70 | |
| | 71 | |
| | 72 | |
| | 73 | |
| | 74 | If you want to use volunteer computing, you have two options: |
| | 75 | |
| | 76 | # C |
| | 77 | |
| | 78 | |
| | 79 | k .'<p></p>'. |
| | 80 | tra("%1 Universities%2: use BOINC to create a %3Virtual Campus Supercomputing Center%4.", |
| | 81 | "<b>", "</b>", |
| | 82 | "<a href=\"trac/wiki/VirtualCampusSupercomputerCenter\">", "</a>" |
| | 83 | ) |
| | 84 | .'<p></p>'. |
| | 85 | tra("%1Companies%2: use BOINC for %3desktop Grid computing%4.", |
| | 86 | "<b>", "</b>", "<a href=https://boinc.berkeley.edu/trac/wiki/DesktopGrid>", "</a>" |
| | 87 | ) |
| | 88 | .'<p></p> |
| | 89 | |
| | 90 | |
| | 91 | <a class="btn btn-xs btn-primary" href=trac/wiki/BoincDocker>'.tra("BOINC and Docker").'</a> |