1) Message boards : CMS Application : CMS@Home difficulties in attempts to prepare for multi-core jobs (Message 49971)
Posted 9 hours ago by Crystal Pellet
Post:
My experience is that the main process, cmsRun, spawns four threads, each running cmsExternalGenerator, so in your "top" display (Alt-F3) you should see four cmsExternalGenerator processes running at nearly 100% each, with the occasional appearance of the cmsRun master process as it gets its share of the resources..
Did you read my post ? Especially the last sentence:
A 24-core VM was created (no limit) and I see 2 processes cmsRun (each ~14% CPU) and 8 processes cmsExternalGene each consuming ~96% CPU.

The 2 cmsRuns are constantly running using ~13-15% CPU, during a whole run of the 8 cmsExternalGenerator processes.
2) Message boards : Theory Application : Long running task, how to proceed? (Message 49966)
Posted 18 hours ago by Crystal Pellet
Post:
This is the info of the job you're running: pp mb-inelastic 7000 - - pythia8 8.302 vincia-default 100000 1156
That means that 100000 events should be processed and you have done only 700 so far in 4 days.
When you did not restart the VM (several times) it's time to abort the task.
3) Message boards : CMS Application : CMS@Home difficulties in attempts to prepare for multi-core jobs (Message 49965)
Posted 19 hours ago by Crystal Pellet
Post:
I'll give this multi-core on production server a try.
First three tasks had an error cause the new downloaded CMS_2022_09_07.vdi had the same UUID as that one from the dev-system.
I resetted the dev-project on my PC and removed the hard disks from VirtualBox media.
I also removed my app_config.xml to see what is coming from the server without intervention.
I had set 1 task and no limit on CPUs in my project-preferences.
Now the task started OK and after a while started processing internal jobs.
A 24-core VM was created (no limit) and I see 2 processes cmsRun (each ~14% CPU) and 8 processes cmsExternalGene each consuming ~96% CPU.
4) Message boards : Number crunching : VirtualBox ^^#__ 7.0.16 __#^^ (released April 16 2024) (Message 49959)
Posted 1 day ago by Crystal Pellet
Post:
Successful Theory test-task for Windows VirtualBox version 7.0.16

https://lhcathome.cern.ch/lhcathome/result.php?resultid=409549939
5) Message boards : Theory Application : No Tasks (Message 49935)
Posted 7 days ago by Crystal Pellet
Post:
I am not getting any for Windows now, I have the project selected and Vbox installed, site says there are loads but nothing downloading?
Do you have 'native' selected in your project preferences?
6) Message boards : CMS Application : CMS@Home difficulties in attempts to prepare for multi-core jobs (Message 49835)
Posted 24 days ago by Crystal Pellet
Post:
I changed my prefs to 1 task and max 2 CPUs.
The task created a dual core VM with 2792 MB memory.
After about 5 minutes a cmsRun appeared using up to 100% CPU and after another 2 minutes cmsRun started using up to 200% CPU.

First test task: https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=3310818
I tried the same prefs which CP is describing above. However, without success - no dual core VM created :-(
see here: https://lhcathome.cern.ch/lhcathome/result.php?resultid=408217329

what's going wrong?

The multi core CMS is tested on the development system only, afaik ...
... and don't use app_config.xml for CMS.
7) Message boards : CMS Application : CMS@Home difficulties in attempts to prepare for multi-core jobs (Message 49832)
Posted 25 days ago by Crystal Pellet
Post:
I changed my prefs to 1 task and max 2 CPUs.
The task created a dual core VM with 2792 MB memory.
After about 5 minutes a cmsRun appeared using up to 100% CPU and after another 2 minutes cmsRun started using up to 200% CPU.

First test task: https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=3310818
8) Message boards : CMS Application : CMS@Home difficulties in attempts to prepare for multi-core jobs (Message 49830)
Posted 25 days ago by Crystal Pellet
Post:
myself wrote:
Is this cmsRun twice as fast as a single run or is it running two jobs in the background?.

A CMS-job running inside the VM is obviously running twice as fast.
Normally a job needs about 4 hours on my laptop depending on other BOINC-tasks. The BOINC-task is running now 2.75 hours and at least busy with the second cmsRun (65 minutes into that)
9) Message boards : CMS Application : CMS@Home difficulties in attempts to prepare for multi-core jobs (Message 49827)
Posted 25 days ago by Crystal Pellet
Post:
My laptop is configured as a host with 8 cores and I set in project preferences no limit on CPUs and asking 1 task.
The CMS task takes all 8 cores and creates an 8-core VM (8168 MB Base Memory).I'm not using an app_config.xml.
All other running BOINC-tasks are getting the status waiting to run.
After an init-phase of 13 minutes cmsRun started and is using 200% CPU.
Is this cmsRun twice as fast as a single run or is it running two jobs in the background?
No Console outputs to check what's going on.
10) Message boards : CMS Application : CMS@Home difficulties in attempts to prepare for multi-core jobs (Message 49817)
Posted 27 days ago by Crystal Pellet
Post:
Why two? Can we delete the first .vdi?
No. The *_prod belongs to LHC@home and the other vdi to -dev.
In principle they are equal, but each vdi needs an own UUID for VirtualBox to work properly.
11) Message boards : CMS Application : CMS@Home difficulties in attempts to prepare for multi-core jobs (Message 49775)
Posted 15 Mar 2024 by Crystal Pellet
Post:
I think multi-core not yet arrived. Not sure what I could see, because the Consoles do not display usefull info.
I created a dual core VM (not 4 cause other duties on that laptop), but I see only 1 cmsRun using 100% CPU and some other cpu-usage from other processes.
Total 102% CPU after 24 minutes.
12) Message boards : CMS Application : since about 2 hours: all tasks failing after few minutes (SOLVED) (Message 49767)
Posted 13 Mar 2024 by Crystal Pellet
Post:
This morning CMS is running OK for me.
13) Message boards : CMS Application : since about 2 hours: all tasks failing after few minutes (SOLVED) (Message 49755)
Posted 12 Mar 2024 by Crystal Pellet
Post:
Now the problem is not getting the X509 credentials from LHC@home and vLHC@home-dev
14) Message boards : CMS Application : since about 2 hours: all tasks failing after few minutes (SOLVED) (Message 49752)
Posted 12 Mar 2024 by Crystal Pellet
Post:
After the failing connection:

Guest Log: NCAT DEBUG: Using system default trusted CA certificates and those in /usr/share/ncat/ca-bundle.crt.
Guest Log: NCAT DEBUG: Unable to load trusted CA certificates from /usr/share/ncat/ca-bundle.crt: error:02001002:system library:fopen:No such file or directory
15) Message boards : Sixtrack Application : Tasks available / tasks not available (Message 49716)
Posted 5 Mar 2024 by Crystal Pellet
Post:
New sixtrack tasks are now available!
Today again!
16) Message boards : ATLAS application : Extreme event processing times (Message 49713)
Posted 5 Mar 2024 by Crystal Pellet
Post:
Two of them are ready: 111- and 112-thousand cpu seconds for 400 events
17) Message boards : Theory Application : file_xfer_error (Message 49712)
Posted 5 Mar 2024 by Crystal Pellet
Post:
But it still carried on for another 10 days before failing?
It did not really start, so it cannot fail.
The Virtual Machine for this task got a shutdown signal from vboxwrapper. Default is after 864.000 seconds (10 days),
but if you see a Theory task running without CPU it's better to kill such a task.
If you like hanky panky: such a task could be saved by
- suspend the task without leave in memory set - The task wll be saved to disk.
- remove the saved state with VirtualBox Manager
- start the task with VBox Manager
- After the task is processing his first events, stop the task with VBox Manager (save to disk)
- Start the task again with BOINC Manager.
18) Message boards : ATLAS application : Extreme event processing times (Message 49710)
Posted 5 Mar 2024 by Crystal Pellet
Post:
Crystal,
what do you see under properties of the boincmanager for this Task?


Application
ATLAS Simulation 3.01 (vbox64_mt_mcore_atlas)
Name
wPiKDmjlS14nsSi4apGgGQJmABFKDmABFKDm8QvSDm4luLDmYCOiSn
State
Running
Received
3/5/2024 7:09:36 AM
Report deadline
3/12/2024 7:09:37 AM
Resources
8 CPUs
Estimated computation size
43,200 GFLOPs
CPU time
1d 05:57:55
CPU time since checkpoint
00:05:59
Elapsed time
04:39:27
Estimated time remaining
03:18:08
Fraction done
58.512%
Virtual memory size
116.62 MB
Working set size
4.69 GB
Directory
slots/0
Process ID
2116
Progress rate
12.600% per hour
Executable
vboxwrapper_26206_windows_x86_64.exe
19) Message boards : ATLAS application : Extreme event processing times (Message 49705)
Posted 5 Mar 2024 by Crystal Pellet
Post:
This morning I've several tasks running with the 'normal' 400 events,
but after some normal runtimes, I now have tasks with processing times for each seperate event up to 6700 seconds.
Since the logging from ALT-F2 is still stuck, I've no idea of the average event runtime.
20) Message boards : Theory Application : file_xfer_error (Message 49704)
Posted 5 Mar 2024 by Crystal Pellet
Post:
Boinc hasn't been paused much in that time, the chip is a 3950x, any idea why its seemingly been idle then whilst reporting working?

This is the reason: 2024-02-23 14:23:35 (2189670): Guest Log: Probing /cvmfs/sft.cern.ch... Failed! - 2 minutes and 10 seconds after the start.

At that moment your system could not connect to CERN.

Unfortunately, the software is not written so that after ... retries the task is aborted automatically


Next 20


©2024 CERN