LHC@home

Hi, I'm receiving Atlas tasks that are supposed to run on 8 cores, but each task is actually using much less than 1 core.

Boinc takes up space as an 8-core task that is being used, but the reality is that the 4 Atlas tasks to 8 cores =32 theats that are 100% of my CPU only use 2%. Furthermore, all that free CPU performance that is not being used cannot be used to perform other tasks. Atlas Tasks are now much slower to achieve a result.

In my opinion, you put a core limiter on the tasks / a partial use in CPU performance x time per thread.

ID: 10873336 computer
https://imgur.com/a/RTMmCVV

https://imgur.com/a/hQkvXri

Consider to upgrade your VirtualBox.
Your version is 7.0.6 which is not supported any more according to the changelog:
https://www.virtualbox.org/wiki/Changelog-7.0

Before you do the upgrade ensure there's no VM currently running or in saved state.

If you get the same errors after the upgrade your vdi image may be damaged.
In that case
- set your client to "no new tasks"
- cancel all LHC tasks and report them
- reset the project
- allow new work

Thanks. Recently I've been suffering a similar problem with running tasks that are nearly complete dropping from 4-cores to 1-core and the remaining extending dramatically from a few minutes to several hours along with the progress barely incrementing (say 0.001% per minute).

So time to update Virtual Box from its current 7.0.14 to whatever the latest (and best?) is. The link you give goes to the 7.0.26 change text page, and has a warning that versions 7.0.x are no longer supported, and there is no (obvious) link to download that version. Checking on the "download" page the current version is 7.2.2, again with no obvious way of downloading historic versions.
So, the questions are:
Is 7.2.2 a "good version, will it run under Windows 10, do I download the "Windows Hosts" package, run that and keep my fingers crossed?

In most cases the main page of a website provides relevant links.
In case of VirtualBox their main mage links to the download overview:
https://www.virtualbox.org/

On that page scroll down and and find a link to "Previous Releases" bottom right:
https://www.virtualbox.org/wiki/Downloads

... The link you give goes to the 7.0.26 change text page ...

Not only.
It presents the whole 7.0.x changelog.
Just scroll down.

Recently I've been suffering a similar problem with running tasks that are nearly complete dropping from 4-cores to 1-core and the remaining extending dramatically from a few minutes to several hours along with the progress barely incrementing (say 0.001% per minute).

Ignore BOINC's progress bar.
BOINC doesn't know what's going on inside the VM.

Your walltimes compared to the CPU times typically show an efficiency around 90 %.
Thats pretty good.
ATLAS uses 1 core during startup and at the end of the calculation phase when there's only 1 unfinished event in progress.
It also runs on 1 core during stage-out.
Unused cores allocated by the VM remain idle until the task ends.
"Several hours" seem to be a myth. Your logs don't confirm that.

I am running tests with Windows 11 wsl2 /Docker/Boinc without adjusting anything except a few instructions in windows "enable or disable Windows features", it seems to work with Xtrack tasks but only with those, and it struggles to receive tasks to reach 32 threads.

With everything enabled in Windows 11 except for certain Windows features settings, it runs really fast. Don't you think about converting the software and using Docker?

Months trying to get VirtualBox and BOINC to work on my Windows 11 and it was never possible, then I came across DOCKER AND SURPRISE, following the guide was very easy.

https://github.com/BOINC/boinc/wiki/Installing-Docker

windows10 Full

---