LHC@home

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.

Crystal,
what do you see under properties of the boincmanager for this Task?

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.

I can't access Alt-F2 on my system either. However there may be a way to bypass that, and still get all the info you need.
Are you running Linux on your system? If so, is BOINC running as a system service? If it is, I can give you instructions so you can access the same information using the VirtualBox Manager.

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

Very good,
do waiting for finish. You get a few cobblestones ;-))

Two of them are ready: 111- and 112-thousand cpu seconds for 400 events

The Threadripper use 6 Cpu's, running in 6 hours with 36 hours Cpu for this heavy Atlas-Tasks.
Something for a Cray.