Changes between Version 1 and Version 2 of MultiHost
- Timestamp:
- Apr 24, 2007, 7:34:05 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MultiHost
v1 v2 1 1 = Increasing server capacity = 2 2 3 3 The BOINC server software is designed so that a project with tens of thousands of volunteers can run on a single server computer. However, the capacity of this computer may eventually be exceeded. Symptoms of server overload include: 4 4 * dropped connections 5 5 * slow web site access … … 7 7 * database queries take minutes or hours to complete. 8 8 9 BOINC has a scalable server architecture that lets you increase server capacity by adding more computers. The steps are as follows. 9 BOINC has a scalable server architecture that lets you increase server capacity by adding more computers. The steps are as follows. 10 10 11 == Run MySQL on a separate host == 11 12 When you initially create a BOINC project using [http://boinc.berkeley.edu/make_project.php make_project], everything runs on a single host: MySQL database server, web server, scheduling server, daemons, tasks, and file upload handler. Of these tasks, the MySQL server does the most work (typically as much as all the others combined). So, if you need to increase the capacity of your server the first step is to move the MySQL server to a separate host (preferably a fast computer with lots of memory). Specify this host in the [http://boinc.berkeley.edu/project_options.php project configuration file]. 12 13 13 14 14 15 == Run server daemons and tasks on multiple hosts == 15 16 If you need more server capacity, you can move some of the server [http://boinc.berkeley.edu/project_daemons.php daemons] and [http://boinc.berkeley.edu/project_tasks.php tasks] to separate hosts. (Start by moving the one that's doing the most work). 16 17 17 18 When you move daemons and tasks to other hosts, those hosts must satisfy the following rules: 18 19 19 20 20 * The [http://boinc.berkeley.edu/groups.php project admin account] must exist on all hosts, and a user must be able to use 'ssh' to run commands on any other host without typing a password. 21 21 * The hosts must share a common network file system, and path to the project directory relative to the project admin's home directory (typically ~/projects/PROJECT_NAME) must be the same on all hosts. 22 * One host is designated as the project's '''main host''' in config.xml. '''The 'start', 'stop', and 'status' scripts should normally 23 be run on the main host''' (if you run them on a different host X, they'll affect only daemons and tasks on host X). 22 * One host is designated as the project's '''main host''' in config.xml. '''The 'start', 'stop', and 'status' scripts should normally be run on the main host''' (if you run them on a different host X, they'll affect only daemons and tasks on host X). 24 23 * The project admin account on all hosts must be able to access the project's MySQL database. (Exception: data servers and file upload handlers don't need DB access). 25 24 26 25 Host locations are specified as follows: 27 26 * Scheduling servers are listed in the project's [http://boinc.berkeley.edu/server_components.php master page]. 28 27 * The hosts on which tasks and daemons are run are specified in the [http://boinc.berkeley.edu/configuration.php config.xml] file. … … 33 32 34 33 == Parallelize schedulers and daemons == 35 34 If you need even more server capacity, you can parallelize most of the BOINC daemons so that multiple instances run on a single (multiprocessor) host, or on different hosts. For example, the following [http://boinc.berkeley.edu/project_daemons.php config.xml] entries run two instances of the transitioner on the host 'kosh'. Because these instances are on the same host, you must specify different output and PID files. 36 35 {{{ 37 36 <daemon> … … 48 47 </daemon> 49 48 }}} 50 49 You can run scheduling servers on multiple hosts by running an instance of the feeder on each host, and including the URLs in your master file.
