but Boinc does not do all that much disk IO as to slow me down much.

It depends on the application.
In the case of Rosetta, the Rosetta 4.20 Tasks don't require much disk I/O, however the Python Tasks require massive amounts of disk I/O when starting up & ending. And apparently they also require quite a bit during processing. The more cores & threads a system has & uses, then the higher the disk I/O requirements will be.

LHC aswell.

Looking at this message was a reminder to do all this.
No new .tmp files, freed up a few Gb here too, grabbed Treeview but it's not telling me anything I expect to find useful so removed again.
I've got BoincTasks but hadn't set it up to run at startup, which I've now done. Yes, very useful in finding tasks that are very far behind in CPU time compared to Elapsed time.
More useful when running VBox tasks compared to running plain Rosetta tasks - I'll keep this going now.
All good, ta

I assume you used treeSIZE. That one is great, it's like a windows explorer tree, but with sizes. I removed a whole load of stuff *I* had put there that I didn't need. Games I no longer played, films that can be archived onto the rust spinner, etc.

No idea how people can manage with just the plain Boinc Manager, it's absolutely horrid, especially if you have a lot of tasks. No colour coding, no grouping of queued tasks, etc. And with me having 7 computers, I really need a central controller. At least Folding at Home supplies such a thing, but I don't think the Boinc Manager will look at many computers easily.

Update: The first task to be postponed reached the end of its one day postponement, and now appears to be computing successfully (in VBox 6.1.34). Haven't tried reverting to previous version to see what happens, but whatever the problem was it seems to have resolved.

I may have spoken too soon. The tasks were running for exceptionally long times (18-26 hours) - although unlike the normal "not doing anything" vbox tasks, they were showing significant CPU time utilised (rather than the tasks that "run" for 18 hours but have only consumed 10-20 seconds of CPU). I shut down BOINC, rolled VBox back to version 6.1.12 (BOINC recommended version, not 6.1.32 which I had been running), restarted, and all the vbox tasks came up with computation errors.

Oh well, will see what happens with the next tasks to run.

I'm on VB version 5 (or Cosmology breaks completely) and it seems to run Rosetta Python just as well as 6. LHC is also happy with it. Kryptos at Home also hates 6. Seems like VB screwed up when they made the new one.

Does QuChempedia hate vbox 6 too?

Does QuChempedia hate vbox 6 too?

Never heard of it, let alone used it. Can't test here as I have VB 5 on everything.

https://boinc.berkeley.edu/projects.php#:~:text=Details-,QuChemPedIA%40home,-%D0%A4%D0%B8%D0%B7%D0%B8%D0%BA%D0%B0

Does QuChempedia hate vbox 6 too?

Thanks for telling me about that one, I was looking for a chemistry project! If you use windows you have to turn on beta tests, as only linux is non-beta.

Does QuChempedia hate vbox 6 too?

Never heard of it, let alone used it. Can't test here as I have VB 5 on everything.

Vbox per project is not relevant.
It is a matter of does the project run their tasks with Vbox
In this case yes it does use Vbox
| QuChemPedIA@home | Finished download of vboxwrapper_26200_windows_x86_64.exe
You can also check this page [url]https://boinc.berkeley.edu/projects.php [/url] to see if your project choice uses Vbox or not. The blue box symbol at the end of the icon list is for Vbox.


Have to try QuChem again, last time it was not stable enough to run on my system with other projects.

https://boinc.berkeley.edu/projects.php#:~:text=Details-,QuChemPedIA%40home,-%D0%A4%D0%B8%D0%B7%D0%B8%D0%BA%D0%B0

I think I hadn't looked through that list since I set up Boinc originally.

Does QuChempedia hate vbox 6 too?

Never heard of it, let alone used it. Can't test here as I have VB 5 on everything.

Vbox per project is not relevant.

We were discussing VB version 6 messing things up. It breaks Cosmology, I have to use 5.

Does QuChempedia hate vbox 6 too?

Never heard of it, let alone used it. Can't test here as I have VB 5 on everything.

Vbox per project is not relevant.

We were discussing VB version 6 messing things up. It breaks Cosmology, I have to use 5.

That's strange. How vbox processes tasks is above my head.
Computermeze or whatever his name is knows more about that kind of stuff.
Have you asked in Cosmo forum at all if anyone knows why 6 does not work?
Maybe post in Github and see what the experts say.

Vbox projects listed:

BOINC@TACC (not worth the time, its leftovers)
Cosmology (as you already know)
LHC@home
QuChemPedIA@home
RNA World (also leftovers or stuff that can not run on the supercomputer they have) so 0 tasks available.
Here at Rosetta

And that's all that is on the list.

nanoHUB@Home too.

I am using VitualBox to build a Linux Virtual Machine that runs OpenSuSE Tumbleweed, a development versio with kernel 5.17.3, frequently updated so I have to reboot it frequently. It runs Einstein@home CPU tasks not being able to use the nVidia GTX1060 board of its Windows 10 host and QuChem, which being a Linux project does not need VirtualBox.
Tullio

---

I can't run Quchem.
It goes to 60% and becomes unstable.
VmJob unmanagable message.
2022-04-25 20:38:52 (2024): VM state change detected. (old = 'running', new = 'paused')
2022-04-25 21:05:27 (2024): VM state change detected. (old = 'paused', new = 'running')
2022-04-25 21:06:03 (2024): Creating new snapshot for VM.
2022-04-25 21:06:11 (2024): Deleting stale snapshot.
2022-04-25 21:06:12 (2024): Checkpoint completed.
2022-04-25 21:10:16 (2024): VM state change detected. (old = 'running', new = 'paused')
2022-04-25 21:14:52 (2024): VM state change detected. (old = 'paused', new = 'running')
2022-04-25 21:16:38 (2024): VM state change detected. (old = 'running', new = 'paused')
2022-04-25 21:32:41 (2024): ERROR: Vboxwrapper lost communication with VirtualBox, rescheduling task for a later time.

And GPU gives me the exit child error on their new pythons.

Maybe there isn't enough ram for python gpu?

Looking at this message was a reminder to do all this.
No new .tmp files, freed up a few Gb here too, grabbed Treeview but it's not telling me anything I expect to find useful so removed again.
I've got BoincTasks but hadn't set it up to run at startup, which I've now done. Yes, very useful in finding tasks that are very far behind in CPU time compared to Elapsed time.
More useful when running VBox tasks compared to running plain Rosetta tasks - I'll keep this going now.
All good, ta

I assume you used treeSIZE. That one is great, it's like a windows explorer tree, but with sizes. I removed a whole load of stuff *I* had put there that I didn't need. Games I no longer played, films that can be archived onto the rust spinner, etc.

No idea how people can manage with just the plain Boinc Manager, it's absolutely horrid, especially if you have a lot of tasks. No colour coding, no grouping of queued tasks, etc. And with me having 7 computers, I really need a central controller. At least Folding at Home supplies such a thing, but I don't think the Boinc Manager will look at many computers easily.

Oops, yes Treesize. I can see how useful it might be, but I keep a pretty tight ship at the best of times, so no need for it here.
I'd used Boinctasks before, but prior to installing VirtualBox, and I didn't have the kind of problems that BoincTasks would solve back then, so it just seemed an unnecessary duplication.
Nothing against it - just not enough going for it with my limited uses. Until now.

---

Maybe there isn't enough ram for python gpu?

48 gigs? not enough?
I got a ACEMD 3 and running ATLAS and Prime Grid and only using 32% of my total RAM
I don't think its RAM.

The STDERR goes on about memory leaks in its setup, but this is fresh RAM (well half new and half less new but not ancient)

I have only 16 gb ram.

I have only 12 GB RAM on thjis Windows 11 PC and can run both rosetta python and QuChem, but not at the same time. QuChem runs also on my Linux Virtual Machine with 8 GB RAM. I could not run rosetta python on it. Now I am running Rosetta 4.20 on the Windows 11 PC.
Tullio

---