LHC@home

Hi,

Does anyone know the current memory requirements per task, for Theory and CMS?

E.G. 2GB per thread/task

I am trying to work out how much RAM I need to run Theory and CMS on a 22c/44t host.

Thanks

For a rough estimate you may use the size of the VMs that are set up by each task.

CMS: 2GB/task
Theory: 630MB/task

Then add a few GB for the OS and the disk cache.

Thanks that's most helpful.

As a side issue, any ideas on why some (or all) VM's produce the error on Theory tasks: 'fail to open the medium with the following ID..'?

This host has already completed some tasks so I would guess its all setup correctly.

Its currently running VirtualBox 6.1.2.

Consider to make your computers visible for other volunteers here:
https://lhcathome.cern.ch/lhcathome/prefs.php?subset=project
This makes it easier to check for setup issues.

I have now made the added hosts visible; its the V4 Xeon that is having these errors.

These are the commands I used to setup VirtualBox:

echo "deb [arch=amd64] https://download.virtualbox.org/virtualbox/debian bionic contrib" | sudo tee -a /etc/apt/sources.list
wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -
apt update
apt install virtualbox-6.1

This is (one of) the error's and its info:

echo "deb [arch=amd64] https://download.virtualbox.org/virtualbox/debian bionic contrib" | sudo tee -a /etc/apt/sources.list

Are you sure there is no typo?
You wrote bionic.
Shouldn't it be boinc?

No typo, its not actually BOINC although it does look kind of similar.

Its my understand that Bionic is the release name for Debian 18.04.

OK, my fault.
Since I prefer opensuse I'm not familiar with the recent naming conventions for debian like linux distributions.

Could you shutdown all currently running VMs (if any) and replace virtualbox-6.1 with virtualbox-6.0?
I noticed some strange behavior caused by changes in 6.1 that might conflict with the vboxwrapper used by LHC@home.
Other users state they don't have problems but I think it's worth to try it out.

I downgraded to 6.0 and that seems to have fixed the error issues now.

Thanks for all your help in these matters.