LHC@home

Hi Team,
Noticed that a machine wasn't using all of it's CPU power and tracked back to something with the CMS tasks.
They have been failing for a while but also preventing other tasks from utilising the PC's resources properly:
https://lhcathome.cern.ch/lhcathome/results.php?hostid=10516481
I've disabled CMS so other projects can ramp the PC up to 100% CPU again, but would be great if you can spot anything up with it so I can re-enable it.
The machine had lots or resources free but for some reason this project was preventing them being used.
Eg 32 threads but BOINC put other projects in a "Waiting for memory" state when there was heaps free, plus was only seeing ~32% of CPU being used.

If there are logs or any assistance I can provide please let me know,
Thanks, Far

Each CMS VM allocates 1 CPU core and 2 GB RAM.
Your computer has 32 cores and 32 GB RAM.
This would allow you to run up to 16*) CMS VMs concurrently and would leave 16 cores idle.
In addition each CMS task makes heavy use of disk I/O and network, both don't need much CPU.


*) Less in reality - even if the BOINC client is configured to use 100% RAM - since the OS and other processes also require RAM.

Thanks, that helps understand the restricted usage of available resources. Wish I could have afforded 64GB of RAM.

However all the CMS50 tasks were failing anyway :-(

If there are logs or anything that is needed to check why please let me know. In case it's a factor, the version of VirtualBox is more recent than the one distributed with Boinc being 6.1.12r139181 (Qt5.6.2)

Hello,
same problem. Theoretically the computer has resources, but it waits for memory with CMS and blocks the loading of other projects. In the project properties comes out this: Application
CMS Simulation 50.00 (vbox64)
First name
CMS_1538738_1607610862.401591
State
Waiting for memory
Received
Thursday, December 10, 2020, 5:31:55 PM
Deadline for reporting
Saturday, January 9, 2021, 5:31:54 PM
Estimated computation
1,000,000 GFLOPs
CPU time
10:13:26
CPU time since last control
---
Time elapsed
10:24:46
Estimated time remaining
1d 04:47:11
Fraction performed
58.399%
Virtual memory size
281.63 MB
Work block size
2.79 GB
Directors
slots / 1
Progress rate
5.760% per hour
Executable
vboxwrapper_26196_x86_64-pc-linux-gnu.
I don't know anymore. It seems to me that I will try to disable CMS, to see what happens. I'll tell you

Hola de nou, doncs en avortar la tasca del CMS, el BOINC a començat a acceptar i executar nous treballs.

Hi again, for by aborting the work of the CMS, the BOINC has begun to accept and execute new work.

Memory 5.8 GB on both computers with 8 core system is bare minimum to handle is and few sixtrack task.
You have CMS task running and got valid but aborted last one. Probably it wet other task on waiting for ram.

Please uncheck box for native task and test application. You client got many task failed because CVMFS is not installed. If you want to run virtualbox you only get these task by uncheck native but would suggest to run sixtrack and maybe theory until you added more memory.

Hello Gunde.
I have disabled CMS, ATLAS and native spots; as you told me, and BOINC has started running Theory. I'm also running the GPUGRID project in BOINC, maybe it's too much ?. With Kubuntu 18.04, I had no such issues. They came to me as a result of switching to Kubuntu 20.04, although the change is well worth it. I plan to upgrade the RAM to 24GB, but it won’t be this year. I go to the Linux section, to ask about CVMFS installation issues, thanks.