The new Python application does more than take 3gb of memory per task. It also chews up your disk drives by checkpointing too frequently. Most of the problems and stalls are related to checkpointing. A checkpoint option on the preferences would help.

My SSDs and NVMEs don't mind.

No news??

Crickets. I did not expect any response. dcdc has been quite responsive in the past, but the developers can't be bothered.
The new Python application does more than take 3gb of memory per task. It also chews up your disk drives by checkpointing too frequently. Most of the problems and stalls are related to checkpointing.

>> A checkpoint option on the preferences would help.<<

You can set checkpoint interval in boinc manager prefs to anything you like
such as 3600 seconds is once per hour , etc .

https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=5594

---

https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=5594

Sadly, that is very specific to lhc requiring the use of CERN utilities and the project to set up additional servers to provide additional functionality.

You can set checkpoint interval in boinc manager prefs to anything you like
such as 3600 seconds is once per hour , etc .

I think that vms don't care about checkpoint.

---

Seeing all tasks saying "Running" whilst having been sat at 0% for a day and needing aborting, and then having the machine blacklisted from running more VBox tasks is getting tedious. The VirtualBox tasks aren't fit to be released. VirtualBox multi-attach would presumably solve this by reducing disk usage massively, especially on machines with more cores.

---

The VirtualBox tasks aren't fit to be released. VirtualBox multi-attach would presumably solve this by reducing disk usage massively, especially on machines with more cores.

Lhc_dev project is testing largely this new wrapper.
And seems it works!

---

Seeing all tasks saying "Running" whilst having been sat at 0% for a day and needing aborting, and then having the machine blacklisted from running more VBox tasks is getting tedious. The VirtualBox tasks aren't fit to be released. VirtualBox multi-attach would presumably solve this by reducing disk usage massively, especially on machines with more cores.

Not seeing that here, 95% of them work ok.

I'm only seeing it on 8-core machines. The quad-core and older machines are all fine.

---

I'm only seeing it on 8-core machines. The quad-core and older machines are all fine.

How much RAM are you using? I find things go belly up if you run short of it.

I'm only running it on a 6 core at the moment, the only other one I can run it on is 24 core (which I usually leave off Python due to it being sluggish and I use it for other things), I'll try that one to see what happens.

They all got to 2% just fine on my 24 core Ryzen 9 3900XT.

But I aborted them there because Virtualbox on a PC you're trying to use for anything else is preposterous. Even the mouse cursor is more sluggish than a 286! I don't know what Oracle are playing at but the whole concept of virtual machines is flawed. I only run it on Boinc only machines.

32GB in the two that have issues.

---

..

32GB in the two that have issues.

Should be ok, you need 3GB per task. I had a 6 core 16GB machine and it would run 5 then refuse to start a 6th. Mind you it never went wrong, it just didn't fill the cores.

I only aborted 1 of the last 70 tasks due to sticking.

Pyinstaller new version, 5.7 with a lot of bugfix and new features, for example

Support building native ARM applications for Windows. If PyInstaller is ran on an ARM machine with an ARM build of Python, it will prodice an ARM application.

---