CERN Accelerating science

Feed aggregator

Big discovery by PrimeGrid

News of BOINC - Fri, 11/25/2016 - 05:53
The PrimeGrid project has discovered a new prime number, 10223*231172165+1, which is the largest known Proth prime and the largest known non-Mersenne prime. Read about it in New Scientist and in PrimeGrid's announcement.
Categories: BOINC news

New single-core tasks

Atlas news - Tue, 11/22/2016 - 21:44
Thanks for all your feedback on the future of the single-core app. We have seen that it is useful to keep it, especially for less experienced volunteers who don't want to write xml files to configure how many tasks to run.

Therefore we are directing some of the multicore WU into the single core app. These WU will use only one core but process the same number of events (100) as the multicore WU, so will run for a few hours longer than the previous single-core WU.

We have also cancelled the remaining single-core WU which were faulty or stuck on non-responding hosts. Apologies if you were actively crunching one of those.

In addition we have applied the same restrictions to the single-core app as we have on the multicore app: the minimum version of virtualbox required is 5.0.0 and there is a check that virtualisation is possible on your PC before sending WU. So if you have an old virtualbox or a PC not configured for virtualisation then you will not receive any more WU. Please see Yeti's checklist for more information in case of problems.

Thanks again for your continued contribution!
Categories: Atlas news

Migration to LHC@home

vLHCathome news - Mon, 11/21/2016 - 11:53
Following the Theory simulations added 1 week ago, we have now also deployed the CMS and LHCb applications from the T4T/vLHCathome project on the consolidated, original LHC@home.

Registration of new accounts on the Virtual LHC@home project is therefore closed from now on.

We would like to warmly thank you all for your contributions, and to ask you to continue crunching the VM applications on the LHC@home project!

If you have not already registered there in the past, please connect to:
https://lhcathome.cern.ch/lhcathome

We will keep this old site up for as long as needed. You may detach from the old project at your leasure, and attach to LHC@home instead.

--The team
Categories: vLHCathome news

VM applications

Sixtrack news - Mon, 11/21/2016 - 11:05
Following the Theory simulations added 1 week ago, we have now also deployed the CMS and LHCb applications from the Virtual LHC@home project here on the consolidated, original LHC@home.

Please note that in order to run VM applications in addition to the classic BOINC application Sixtrack, you need to have a 64bit machine with VirtualBox installed and virtualisation extensions (VT-x) enabled. The details are explained on the join us and faq pages on the LHC@home web site.

By default, only the Sixtrack application is enabled in your BOINC project preferences. If you have VirtualBox installed and wish to try VM applications as well, you need to enable other applications in your LHC@home project preferences.

Please note that if you run an older PC with Windows XP or similar, it is recommended to stay with the default; Sixtrack only.

Thanks for your contributions to LHC@home!

--The team
Categories: Sixtrack news

New .NET GUI RPC binding

News of BOINC - Tue, 11/15/2016 - 08:24
If you're interested in building a BOINC GUI in .NET, check out this new .NET binding of the GUI RPCs.
Categories: BOINC news

Single core tasks finished

Atlas news - Thu, 11/10/2016 - 11:50
You may have noticed that there are no single core tasks left in the queue. This is deliberate as part of our aim to simplify things by having a single app which is multicore only.

We know that there are people who like to run only single-core WU but it is possible to run multicore WU in a single-core mode through the use of app_config.xml. (set 1)

This is not a perfect solution so if there are serious objections to deprecating the single core app we can do some tricks to send multicore WU to the single core app which will then run in single-core mode. Please let us know what you think.
Categories: Atlas news

CMS Servers shut down until further notice

vLHCathome news - Mon, 10/24/2016 - 17:50
I have just been informed (and confirmed) that the servers we use at RAL have been shut down due to the CVE-2016-5195 "Dirty COW" Linux kernel vulnerability. They will remain down until a patch is available and applied.
It would be prudent to suspend the CMS application in BOINC until the servers are restarted.
Categories: vLHCathome news

New multi-core version 1.05

Atlas news - Thu, 10/06/2016 - 13:45
The new batch of multicore WU that we have require a new version of ATLAS simulation software so we had to release a new version of the multicore application. The only change is the VM image which unfortunately has grown in size to 2.3GB with the new software.
Categories: Atlas news

LHC@home consolidation

Sixtrack news - Thu, 10/06/2016 - 12:56
As part of consolidation of LHC@home, we have setup a new server web front end using SSL for this project. The new URL is:

https://lhcathome.cern.ch/lhcathome

Please feel free to connect to the new site at your convenience. (BOINC 7.2 clients and later supports SSL.)

The old LHC@home classic site will continue operation as long as required. Currently there are no new Sixtrack tasks in the queue, but soon more applications and work will be available from this project.
Categories: Sixtrack news

SSL connection option

vLHCathome news - Thu, 09/22/2016 - 11:30
For those with BOINC clients above version 7.2, there is now an option to connect with SSL on the URL:

https://lhcathome.cern.ch/vLHCathome/

This server runs a web-front end and scheduler for this project. To use it, please detach fron the project, and re-attach using the new HTTPS URL.

The other project daemons still run on the same server as before. The old server and URL will remain in place until further notice.

So far our tests of this distributed server setup works fine, and we would appreciate feedback in case of problems.
Categories: vLHCathome news

Changes to the multicore app configuration

Atlas news - Tue, 09/13/2016 - 10:09
After analysis of results from the multicore app (see this thread) we have made the following changes

- Minimum VirtualBox version required is 5.0.0
- Maximum cores reduced from 12 to 8 (this can be overridden in app_config.xml but we have seen severe performance issues above 8 cores)
- Enforced that hardware acceleration is enabled on the host. This should stop the -148 ERR_EXEC errors because WU will not be sent to these hosts.

Please continue to provide your feedback on changes we make.
Categories: Atlas news

Removing the restriction on running work units

vLHCathome news - Tue, 09/06/2016 - 15:13
After experimenting with a number of options, a solution has been found to provide a default limit on the number running work units per host for new volunteers which can be disabled by those who are more experienced.

Once implemented, a new setting will be available in the project preferences where the Max # jobs can be set. In order to provide this, three steps are required.

  • Update the project to support the option
  • Updated everyone's project preferences to set this value to 2 tasks
  • Remove current the project limit



This should be transparent for everyone and only those who wish to receive more tasks will get them once they have changed the value of this new setting. Work on this will start immediately and should be completed within the next few days.

Categories: vLHCathome news

Removing the restriction on running work units

vLHCathome news - Tue, 09/06/2016 - 15:13
After experimenting with a number of options, a solution has been found to provide a default limit on the number running work units per host for new volunteers which can be disabled by those who are more experienced.

Once implemented, a new setting will be available in the project preferences where the Max # jobs can be set. In order to provide this, three steps are required.

  • Update the project to support the option
  • Updated everyone's project preferences to set this value to 2 tasks
  • Remove current the project limit



This should be transparent for everyone and only those who wish to receive more tasks will get them once they have changed the value of this new setting. Work on this will start immediately and should be completed within the next few days.

Categories: vLHCathome news

Tips on how to gain better performance on the ATLAS_MCORE app

Atlas news - Tue, 09/06/2016 - 03:23
According to our test, the CPU performance (We measure the CPU performance by seconds of CPU per event. For example, the current ATLAS job running on the ATlAS_MCORE app processes 100 events, if the overall CPU time for this job is 30000 seconds, then the CPU performance is 300 seconds/event) varies to the number of cores of the vm.

In the test, we also compared the CPU performance on different Virtualbox versions.

The test result can be seen here:



Also, we conclude a result from the ATLAS job statistics based on the jobs from over 1 month period. The following result shows the average CPU performance on different number of cores. (ATLAS_MCORE supports up to 12 cores for now).



The benefit of using more cores in one vm is to save memory usage, but using big number of cores can also significantly reduce the CPU performance. Our test result also concludes this is a case in all cloud computing platforms, not just on ATLAS@home.

In order to have a good tradeoff between memory usage and CPU performance, we advise that you configure the cores to each ATLAS_MCORE job(VM) according to the overall cores and memory allocated to BOINC.For example,if your host allocates 12 cores to BOINC, by default, ATLAS_MCORE creates a vm with 12 cores with 12.1GB memory, but if the host has enough memory, you can customize the usage with the app_config.xml file, i.e. each vm uses 6 cores with 7.3GB memory, so that your host runs 2 vms, and the overall memory usage is 14.6GB.

You can limit the MultiCore-App by using the app_config.xml (This file needs to be put in your project/atlasathome.cern.ch/ directory).

Below is an example to limit each ATLAS_MCORE job to use only 6 Cores:

<app_config> <app_version> <app_name>ATLAS_MCORE</app_name> <avg_ncpus>6.000000</avg_ncpus> <plan_class>vbox_64_mt_mcore</plan_class> <cmdline>--memory_size_mb 7300</cmdline> </app_version> </app_config>

You should change these two lines to your needs:

<avg_ncpus>4.000000</avg_ncpus> <cmdline>--memory_size_mb 7300</cmdline>

Memory usage calculated by the ATLAS_MCORE app is by this formula:

memory = 2500 + (800* NumerOfCores)

so it is 7300MB for 6 cores.

We will also make some changes on the server side very soon:
1. Require a minimum version(5.0.0) of Virtualbox for the ATLAS_MCORE app.
2. Limit the ATLAS_MCORE app to use at most 8 cores.
Categories: Atlas news

Performance issues with older Virtualbox

Atlas news - Thu, 09/01/2016 - 10:46
We recently noticed that with the ATLAS Multi Core application, there is a HUGE performance difference between the old and new version virtualbox, and this is especially obvious with big multi core (Core number >4 ).


As shown in this host with 12 Cores allocated to BOINC, the older version of virtualbox (4.2.16) uses almost 3 times of CPU time compared to the newer version(5.1.2) with the same kind of jobs.More results of other hosts from our database confirms this difference. And our database also shows around 7% of hosts still use older virtualbox(version<5.00). In order to avoid wasting the CPU, we advise that you upgrade the virtualbox to the most recent ones (5.1.2 or 5.1.4).

Also, in a few days, we shall setup a requirement on the server, so that hosts with older virtualbox(version<5.0.0) no longer receives the ATLAS Multi Core jobs.
Categories: Atlas news

Moving multicore out of beta on Mon 29th August

Atlas news - Fri, 08/26/2016 - 13:27
We intend to move the multicore app out of beta on Monday the 29th August. This means that by default everyone will get both singlecore and multicore WU.

The main motivations for this are that multicore provides better CPU and memory efficiency, and we only have to manage a single stream of tasks instead of two.

If you do not want to run multicore you can disable it in your ATLAS@Home preferences in the option "Run only the selected applications"

By default the tasks will use as many cores as you have allocated to BOINC. For tuning the number of cores that the tasks will use you can create an app_config.xml file as described in this thread

At some point we plan to discontinue the singlecore app and run only multicore. The multicore app will also run on 1 core so you can still continue with ATLAS even with a single core.

Happy crunching!
The ATLAS@Home team
Categories: Atlas news

Multi-core version 1.04 with support for VirtualBox 5.1, OS X and graphics

Atlas news - Tue, 08/23/2016 - 13:27
Version 1.04 of the multicore app has been released with the following improvements:

- support for VirtualBox 5.1
- support for OS X (finally!)
- graphics (same as single core app)

Thank you for your continued support of ATLAS!
Categories: Atlas news

3 TRILLION EVENTS REACHED BY TEST4THEORY TODAY !!!

vLHCathome news - Sun, 08/21/2016 - 10:23
Congratulations and thanks to all our volunteers for helping CERN to reach the extremely impressive total of 3 Trillion events successfully simulated on our Theory project.

We have recently received warm testimonials from scientists who use and appreciate the MCPlots database which is the destination of all your work. We have posted these on our "Science" message board at:

http://lhcathome2.cern.ch/vLHCathome/forum_thread.php?id=1889&postid=21037#21037
Categories: vLHCathome news

3 TRILLION EVENTS REACHED BY TEST4THEORY TODAY !!!

vLHCathome news - Sun, 08/21/2016 - 10:23
Congratulations and thanks to all our volunteers for helping CERN to reach the extremely impressive total of 3 Trillion events successfully simulated on our Theory project.

Further announcements and testimonials from our scientists will be posted later!
Categories: vLHCathome news
Subscribe to LHC@home aggregator