As I mentioned in the project nomination thread I don't think Cosmology@Home is a good project for the Pentathlon. They haven't really put out tangible results.
When I crunched it before the estimated time durations are all completely off and I noticed that it has higher memory use. The new virtualbox units seem to be reporting half the cores you have enabled , which is an oddity in itself.
The current admin for the project is new to crunching as of July 2015 ; for a project supposedly backed by major players such as NSF and a worldclass university (University of Illinois at Urbana-Champaign) it is lacking in polish. Ironically the move to Paris as of 2016 has helped it.
Per their revised FAQ:
VT-x/AMD-v for the new app
Cosmology@Home runs multiple “apps.” The requirements list is for the default app (named camb_boinc2docker), but if your computer does not meet them, there is an older app available (named camb_legacy) which runs on just Windows and Linux but supports 32-bit processors and does not need Virtualbox or VT-x/AMD-v. At this point we only use the results from camb_legacy for testing the PICO algorithm and not for comparing with data since the app is fairly old. However, the results do serve a limited purpose and allow Cosmology@Home users who do not meet the above requirements to continue to contribute, thus we continue to provide it. We encourage users who can run camb_boinc2docker to do so, however.
and some settings
I enabled VT-x/AMD-v but jobs say “Scheduler wait: Please upgrade BOINC”
If you attempted to run a camb_boinc2docker job before enabling VT-x/AMD-v, it is possible your client is stuck in a state where it still thinks this feature is disabled. It will give you a message “Scheduler wait: Please upgrade BOINC to the latest version” and the log files will show “ERROR: Invalid configuration. VM type requires acceleration but the current configuration cannot support it.” To fix this:
- Remove the Cosmology@Home project
- Shut down the BOINC client (from Advanced View choose the menu option Advanced->Shutdown Connected Client)
- Go to your BOINC folder and edit the file client_state.xml
- Remove the line which contains
- Restart your BOINC client and readd the project
Edited by AlphaC - 4/30/17 at 7:50am
camb_boinc2docker is multi-threaded and will use up all available cores which BOINC allows it to. For example, if in the BOINC computing preferences you have set “Use at most 50% CPU time” and you have a 4-core processor, the job will use two of them.
If for whatever reason you wish to limit the number of cores used without changing the global BOINC CPU usage, you can do so by creating a file called "app_config.xml" in the Cosmology@Home project folder and adding the following text, with the “2” under avg_ncpus replaced by however many CPUs you want to use (thanks to Crystal Pellet):
If after this BOINC gives an error reading your app_config.xml file, make sure you saved the file with a character encoding apropriate for your system (options to do so may vary by text editor).
You will need to restart your BOINC client for this take effect
This will only affect jobs started after you created the file (jobs started before will show “X CPUs” but still run using all of them, you can just abort these)
Reseting or removing/readding the project will delete this file so you will have to remake it