LHC@home

Hello everyone.

I would like to ask your opinion about the behavior of the computation units I have been processing lately.
It seems that in the final stages of processing, when the estimated remaining time is a few tens of minutes, the execution speed decreases a lot. The example figure shows eight minutes remaining, but the actual processing will still take several hours.

https://i.imgur.com/yJEDBOw.png



The configuration that behaves in this way is as follows. Has anyone experienced the same problem and can give me any suggestions? Thank you.

Libraries: libcurl/7.84.0-DEV Schannel zlib/1.2.12
OpenCL: Intel GPU 0: Intel(R) HD Graphics 620 (driver version 30.0.101.1340, device version OpenCL 3.0 NEO, 6500MB, 6500MB available, 192 GFLOPS peak)
Windows processor group 0: 4 processors
Processor: 4 GenuineIntel Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz [Family 6 Model 142 Stepping 9]
OS: Microsoft Windows 10: Professional x64 Edition, (10.00.19044.00)
Memory: 15.87 GB physical, 26.87 GB virtual
Disk: 465.15 GB total, 168.11 GB free
VirtualBox version: 6.1.36

Have you checked Yeti's Checklist in this folder?

The final stage (and also the starting phase) use only one CPU core even if you have setup the task use multiple cores for crunching.

---

I would like to ask your opinion about the behavior of the computation units I have been processing lately.
It seems that in the final stages of processing, when the estimated remaining time is a few tens of minutes, the execution speed decreases a lot. The example figure shows eight minutes remaining, but the actual processing will still take several hours.

Hello Marco,

For your type of CPU and running ATLAS on 4 threads that long runtime is not normal.
The 200 events to process should take between 8 and 12 hours at the most on that machine.
I noticed from the 2 results you returned that the Virtual Machine is paused and restarted very often.
ATLAS (and CMS) don't like that. They want to run in one flow without interruption. They also always want to have connection to the network.
1 of your results was succesfull (HITS file was successfully produced), the other was valid, but not successful (No HITS file was produced)
BOINC's 'tempo mancante' is useless for VM-tasks progress.
You may better use the VM's Console to watch the progress with the ALT-F3 and ALT-F2 keys.

Thank you Crystal, Harri and maeax for your useful advices.
I'm checking the configuration, hope to start with the tasks again soon.
Have a great day!