Category:Boinc: Difference between revisions
m (→Shared Memory) |
(No difference)
|
Latest revision as of 15:26, 27 May 2005
OSCG and Boinc
Boinc Could be an ideal way to use a cluster of clusters for software development, allowing developers to create and deploy a distributed project without the need of building a user base.
Currently, OSCG is linux/openMosix only so testing could be done only for that OS.
oM Unfriendliness
BOINC is not currently in an oM friendly state.
BOINC uses shared memory to communicate between itself and the projects that run through it which means that it would be nodelocked to the parent machine under the current oM. Work is being done on the MigSHM extension to openMosix which will enable migration of applications that use shared memory. oM-2.6.x should support migration of shared memory by default.
Number of Processes to Run
Another shortcoming of BOINC is that you cannot manually specify the number of processes to run. This means that BOINC will only spawn enough processes to run 1 per each physical CPU in the machine that it is hosted on. We need to communicate with the developers of BOINC to see if we can encourage them to include an optional commandline switch that specifies the number of processes to spawn.
Hosted on
- IND-Network.co.uk
- Currently INACTIVE
If you would like to host this project, please contact the OSCG admin.
Pages in category "Boinc"
The following 2 pages are in this category, out of 2 total.