LHC@home

OK, while we get our heads around various problems, we've decided just to send 4-core tasks for the rest of the week. This means you can suspend or set to NoNewTasks any machine that's not set up to run quad-core VMs.
To enable 4-core tasks, select the locale(s) (default, home, work or school) you want to run 4-core in and make sure the LHCathome preferences for that locale are set to run CMS with Max # CPUs set to 4. You can set Max # Jobs to whatever number your CPUs can run at 4-cores/job. Remember that multicore tasks will take proportionately more bandwidth, memory and other resources than single-core tasks. Check that the machines you want to run are truly set to the desired locale.
At present we have two workflows running. One is set to run 503,000 events/job (as was the template it was derived from) and takes about 5-6 hours wall-time. The other is set to 50,000 events/job and runs about one hour clock time. If we run out of jobs before the weekend, I'll submit a batch with 100,000 events/job, to match the 2-hour average our previous tasks took. These jobs generate considerably less output per CPU-hour than our previous ones.
I've noticed a few curious things with VirtualBox -- some people have not been running the VirtualBox extension pack, so make sure you are running the same version extension pack as your VirtualBox executable. I've also seen some errors activating the "multiattach" feature we use (where more than one VM can use the same virtual-disk image) with the claim being that it only works for vdis created with VirualBox greater than 4.0.

---

some people have not been running the VirtualBox extension pack

It is not a must to install the extension pack if you just want to run a headless VM.

I've also seen some errors activating the "multiattach" feature we use...

This is most likely solved with the upcoming new vboxwrapper version from github.
I'll inform Laurence as soon as it is approved and merged over there.

Cores per work unit set to four: check
Machine on correct profile: check
Guest Extensions correct version: check (VBox Version 7.0.16 r162802 (Qt5.15.3) )
Work fetch enabled: check
Abort all existing single core work units: check
Request fresh work: check
Check stderr for running CMS work unit: only requests single core and VM only allocates a single core, VBox Extension Pack recognised
Check VBox manager: all VMs show Extension pack available

Something isn't right.

Reset project: still not downloading the CMS multithread vdi

Running job output should appear here.......
Now 20 Minutes.https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=3323207
Properites
Ressourcen
4 CPUs
Geschätzter Berechnungsaufwand
1.000.000 GFLOPs
Prozessorzeit
01:08:41
Prozessor-Zeit seit dem letzten Checkpoint
00:52:06
bisherige Laufzeit
00:33:36
Geschätzte verbleibende Zeit
07:52:54
Fortschritt
3,082%

It working!

2024-04-24 22:17:02 (1865718): Setting Memory Size for VM. (2048MB)
2024-04-24 22:17:02 (1865718): Setting CPU Count for VM. (1)

Still NOT working
https://lhcathome.cern.ch/lhcathome/result.php?resultid=410235598

Without Proxy, the same?

Still NOT working
https://lhcathome.cern.ch/lhcathome/result.php?resultid=410235598

The task was running, but there are no single core CMS jobs at the moment: https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=6112&postid=50025

Without Proxy, the same?

I'll try disabling the proxy, but the new vdi has a different name and isn't being requested as far as I can tell.

Turned off proxy in Boinc manager, reset project. Still only downloading the CMS_2022_09_07_prod.vdi and not the 70.20 (vbox64_mt_mcore_cms) one.
Turning proxy back on now.

Greetings,

Grabbed a 4 core multi, just now, to test my setup.

Showing in boinc as a multi-core.

Cheers

Grabbed a 4 core multi, just now, to test my setup.

you were lucky, there was obviously just a short time period around 8 a.m. when jobs were available.
From what I can see the task is still running

Morning,

Task details at below link

https://lhcathome.cern.ch/lhcathome/result.php?resultid=410305137

Cheer

Some of us REALLY need the option to disable single core CMS work. I'm still getting nothing but the single core wrappers. Project reset does nothing but force me to download hefty vdi files over again and still gives me single core CMS. Multi threaded Atlas native works fine.

Greetings,

I came across something bit strange, well I was helping out a team member at the same time, but here goes,

My Windows 11 machine will download and run 4 core multicore CMS workunits.

My Linux Mint 21.3 machine will only download and run single core CMS workunits.

Am I missing something here though?

Regards

Production:
Microsoft Windows running on an AMD x86_64 or Intel EM64T CPU 70.20 (vbox64_mt_mcore_cms)
-dev
Microsoft Windows running on an AMD x86_64 or Intel EM64T CPU 61.01 (vbox64_mt_mcore_cms)

This -dev Version is from yesterday.
Thinking Laurence and his Team (including Ivan) will see first how it work in -dev.
First task in -dev finished:
Computer ID 4639
Laufzeit 6 Stunden 59 min. 28 sek.
CPU Zeit 1 Tage 0 Stunden 58 min. 31 sek.
Prüfungsstatus Gültig
Punkte 1,101.22

I finally got some linux mt units.
Only ended up resetting the project several times and nuking eleven hundred plus empty single core units to finally get there.

maeax wrote:

...
Laufzeit 6 Stunden 59 min. 28 sek.
CPU Zeit 1 Tage 0 Stunden 58 min. 31 sek.
Prüfungsstatus Gültig
Punkte (=credit points): 1,101.22

Excerpt from the finished task from colleague tazzduke, a few postings above, this morning:

Laufzeit 14 Stunden 14 min. 48 sek.
CPU Zeit 1 Tage 22 Stunden 41 min. 55 sek.
Prüfungsstatus Gültig
Punkte (=credit points): 31.21

Credit points need to be working sometime with this new Program-Version.

Run time 5 hours 58 min 38 sec
CPU time 14 hours 40 min 18 sec
Validate state Valid
Credit 3.56

Run time 3 hours 9 min 48 sec
CPU time 5 hours 46 min 57 sec
Validate state Valid
Credit 1.88

Run time 5 hours 50 min 56 sec
CPU time 14 hours 38 min 39 sec
Validate state Valid
Credit 3.63

Excuse me, but what??