Rosetta@Home has not these points. WCG (when it was IBM) has.
When IPD/BakerLab needs great computational power that cannot split on Boinc, they always use external source: AWS, Azure, TACC, ecc.

But, maybe i'm wrong.....

You are probably right. It is a question of "when" they need it. I expect it won't be so often now.
However, whether they do or not, they still have periodic shortages, usually in the summer or holiday season. That says they don't have enough work to carry them through.
So they don't need so many crunchers. They will still get the same amount of work done over a period of time. I prefer to put my machines where most needed.
It is just a personal preference.

---

I'm getting "No VBox installed" messages again along with no new work when reporting completed work, and the Ready to send number has taken a dive, so i'm guessing we've already finished off that last batch of Rosetta 4.20 work.

Confirmed here... <sigh>

A load came through a few hours ago and a few more a short while ago, but seems to have run out again

---

I'm getting "No VBox installed" messages again along with no new work when reporting completed work, and the Ready to send number has taken a dive, so i'm guessing we've already finished off that last batch of Rosetta 4.20 work.

Confirmed here... <sigh>

A load came through a few hours ago and a few more a short while ago, but seems to have run out again

At the time of this message its 0.
4986 python if you can manage to get any.

I pointed that out about a year ago when MIP on WCG (which uses Rosetta) went in-house. They didn't need the crunchers any more.

I don't think so.
In-house HPC needs some points:
- a lot of performative hardware
- a big and prepared IT team
- simulations as much as possible homogeneous

Rosetta@Home has not these points. WCG (when it was IBM) has.
When IPD/BakerLab needs great computational power that cannot split on Boinc, they always use external source: AWS, Azure, TACC, etc.

But, maybe i'm wrong.....

I wondered where TACC got their BOINC stuff. It's so spotty there, not worth wasting you time.
It might be time to say goodbye to RAH.
All this BS that is going on, it's starting to make me rethink staying here.
I've been grinding a long time for them, its a shame to leave.

I am out, until someone can confirm that the pythons are working correctly, and I can select them.

Part one of that is no problem.
I returned at least two proper results before the one I was complaining about.
Unfortunately I can't show them off anymore, as the db seems to have taken them out by now.
vbox can be a hassle on every project, and I encountered similar problems elsewhere.
Dealing with projects that have nothing except vbox apps is one thing, but Rosetta isn't one of those.
So the possibility to unselect those monsters should obviously and absolutely be existing!

I can confirm that the Python tasks work just fine on my Windows 11 beta testing laptop, I am running ver 6.1.26 of VBox and ver 7.16.20 of Boinc:

1450357706 1293408677 4767328 17 Nov 2021, 0:09:28 UTC 20 Nov 2021, 0:09:28 UTC In progress --- --- --- rosetta python projects v1.03 (vbox64)
windows_x86_64
1450297317 1293408267 4767328 17 Nov 2021, 0:09:28 UTC 20 Nov 2021, 0:09:28 UTC In progress --- --- --- rosetta python projects v1.03 (vbox64)
windows_x86_64
1450357611 1293408634 4767328 17 Nov 2021, 0:08:51 UTC 17 Nov 2021, 12:13:59 UTC Cancelled by server 0.00 0.00 --- rosetta python projects v1.03 (vbox64)
windows_x86_64
1450286960 1293407997 4767328 17 Nov 2021, 0:08:03 UTC 20 Nov 2021, 0:08:03 UTC In progress --- --- --- rosetta python projects v1.03 (vbox64)
windows_x86_64
1450357628 1293408478 4767328 17 Nov 2021, 0:08:03 UTC 20 Nov 2021, 0:08:03 UTC In progress --- --- --- rosetta python projects v1.03 (vbox64)
windows_x86_64
1449564483 1293454887 4767328 15 Nov 2021, 23:25:48 UTC 17 Nov 2021, 12:12:47 UTC Completed and validated 22,488.82 20,606.27 185.74 rosetta python projects v1.03 (vbox64)
windows_x86_64
1449564347 1293454813 4767328 15 Nov 2021, 23:25:48 UTC 18 Nov 2021, 23:25:48 UTC In progress --- --- --- rosetta python projects v1.03 (vbox64)
windows_x86_64
1449486504 1293416591 4767328 14 Nov 2021, 3:21:18 UTC 17 Nov 2021, 5:45:55 UTC Completed and validated 34,804.85 31,782.95 441.35 rosetta python projects v1.03 (vbox64)
windows_x86_64
1449487643 1293416839 4767328 14 Nov 2021, 3:20:38 UTC 16 Nov 2021, 13:32:46 UTC Completed and validated 40,661.08 40,217.94 515.61 rosetta python projects v1.03 (vbox64)
windows_x86_64
1449487583 1293416824 4767328 14 Nov 2021, 3:20:38 UTC 16 Nov 2021, 19:56:35 UTC Completed and validated 22,768.22 20,693.41 186.15 rosetta python projects v1.03 (vbox64)
windows_x86_64

I'm on 6.1.28 Vbox and 7.16.20 BOINC and not getting anything Python. So weird.

I can see the number 4986 but I can't see that it's a pythron unit. Is it an assumption or do I look the wrong place (Computing drop down menu, Server status)?

Scroll down on the Server Status page to "Tasks by Application" - Rosetta Python Projects.

---

I am out, until someone can confirm that the pythons are working correctly, and I can select them.

Part one of that is no problem.
I returned at least two proper results before the one I was complaining about.
Unfortunately I can't show them off anymore, as the db seems to have taken them out by now.
vbox can be a hassle on every project, and I encountered similar problems elsewhere.
Dealing with projects that have nothing except vbox apps is one thing, but Rosetta isn't one of those.
So the possibility to unselect those monsters should obviously and absolutely be existing!

I can confirm that the Python tasks work just fine on my Windows 11 beta testing laptop, I am running ver 6.1.26 of VBox and ver 7.16.20 of Boinc:

1450357706 1293408677 4767328 17 Nov 2021, 0:09:28 UTC 20 Nov 2021, 0:09:28 UTC In progress --- --- --- rosetta python projects v1.03 (vbox64)
windows_x86_64
1450297317 1293408267 4767328 17 Nov 2021, 0:09:28 UTC 20 Nov 2021, 0:09:28 UTC In progress --- --- --- rosetta python projects v1.03 (vbox64)
windows_x86_64
1450357611 1293408634 4767328 17 Nov 2021, 0:08:51 UTC 17 Nov 2021, 12:13:59 UTC Cancelled by server 0.00 0.00 --- rosetta python projects v1.03 (vbox64)
windows_x86_64
1450286960 1293407997 4767328 17 Nov 2021, 0:08:03 UTC 20 Nov 2021, 0:08:03 UTC In progress --- --- --- rosetta python projects v1.03 (vbox64)
windows_x86_64
1450357628 1293408478 4767328 17 Nov 2021, 0:08:03 UTC 20 Nov 2021, 0:08:03 UTC In progress --- --- --- rosetta python projects v1.03 (vbox64)
windows_x86_64
1449564483 1293454887 4767328 15 Nov 2021, 23:25:48 UTC 17 Nov 2021, 12:12:47 UTC Completed and validated 22,488.82 20,606.27 185.74 rosetta python projects v1.03 (vbox64)
windows_x86_64
1449564347 1293454813 4767328 15 Nov 2021, 23:25:48 UTC 18 Nov 2021, 23:25:48 UTC In progress --- --- --- rosetta python projects v1.03 (vbox64)
windows_x86_64
1449486504 1293416591 4767328 14 Nov 2021, 3:21:18 UTC 17 Nov 2021, 5:45:55 UTC Completed and validated 34,804.85 31,782.95 441.35 rosetta python projects v1.03 (vbox64)
windows_x86_64
1449487643 1293416839 4767328 14 Nov 2021, 3:20:38 UTC 16 Nov 2021, 13:32:46 UTC Completed and validated 40,661.08 40,217.94 515.61 rosetta python projects v1.03 (vbox64)
windows_x86_64
1449487583 1293416824 4767328 14 Nov 2021, 3:20:38 UTC 16 Nov 2021, 19:56:35 UTC Completed and validated 22,768.22 20,693.41 186.15 rosetta python projects v1.03 (vbox64)
windows_x86_64

Can confirm, Windows 11 + VB 6.1.28 + BOINC 7.16.20 and Python tasks run okay. Any hangups have been resolved by quitting and restarting BOINC Manager.

My only complaint is that I can only run one python tasks at a time on my setup and BOINC won't download more tasks to meet by CPU usage settings unless I pause the "waiting to run" Python tasks.

My only complaint is that I can only run one python tasks at a time on my setup and BOINC won't download more tasks to meet by CPU usage settings unless I pause the "waiting to run" Python tasks.

You've got 16GB of RAM on a system with 12 cores/threads. That would cause issues even with some Rosetta 4.20 Tasks, let alone the extreme RAM requirements for Python Tasks.



Edit-
Having said that, has anyone checked how much RAM is being used by VirtualBox in Windows Task Manager? The Python Tasks themselves only use a few hundred MB of RAM, but they do appear to need 8GB+ of storage space.
Has anyone tried giving BOINC 100GB of disk space (for a 6c/12t system) & seeing if those Waiting to run Python Tasks start running?

---

Grant
Darwin NT

My only complaint is that I can only run one python tasks at a time on my setup and BOINC won't download more tasks to meet by CPU usage settings unless I pause the "waiting to run" Python tasks.

You've got 16GB of RAM on a system with 12 cores/threads. That would cause issues even with some Rosetta 4.20 Tasks, let alone the extreme RAM requirements for Python Tasks.

Yeah, you're right, I need way more ram.

Python tasks need like what? 6Gib of RAM each?

BTW, how do I know when to abort a Python task? I may have spoken too soon about W11 playing nicely with Python tasks on my end.

My only complaint is that I can only run one python tasks at a time on my setup and BOINC won't download more tasks to meet by CPU usage settings unless I pause the "waiting to run" Python tasks.

You've got 16GB of RAM on a system with 12 cores/threads. That would cause issues even with some Rosetta 4.20 Tasks, let alone the extreme RAM requirements for Python Tasks.



Edit-
Having said that, has anyone checked how much RAM is being used by VirtualBox in Windows Task Manager? The Python Tasks themselves only use a few hundred MB of RAM, but they do appear to need 8GB+ of storage space.
Has anyone tried giving BOINC 100GB of disk space (for a 6c/12t system) & seeing if those Waiting to run Python Tasks start running?

I've given BOINC 280GB of free disc space. I'll check the actual ram usage of VB Python tasks, it's not that high IIRC. I may have gotten a bad batch of Python tasks that need to be aborted...

Update: Aborted one task that obviously wasn't running right (0% CPU and 0 RAM usage).
boinc_cages_IL_2727241_31732_0 uses 30.5MB of RAM.

Yeah, you're right, I need way more ram.

Python tasks need like what? 6Gib of RAM each?

Maybe...
I'm thinking that's what they insist on to start, and so VBox will take it from the OS and reserve it for that Task. But from the looks of several of your completed Python Tasks, their actual RAM usage is less than 100MB. So in theory, it should be possible for many of them to run at the same time.
VBox reserves 8GB for one Task, it doesn't need it all so when the next Task tries to start, it only needs to pull another 100MB from the OS for two Tasks to be running, with 8GB still available between them. Another Task starts up, only another 100MB is needed from the OS, etc, etc. (Of course i haven't the slightest idea if that's how VBox actually works).

What each Task does require (according to your completed Tasks), is 7.5GB+ of storage space. It looks like each Task needs it's own copy of the VM image in order to run (i'm wondering if this is a repeat of the previous issue with Rosetta 4.xx Tasks when they ran copying all the support files every time a new one started & then deleting them when done instead of just linking to them, or if it's a issue with how VirtualBox works).

I've given BOINC 280GB of free disc space. I'll check the actual ram usage of VB Python tasks, it's not that high IIRC

Thanks for that.
While each Task doesn't use much RAM in it's Virtual Machine, i'm curious as to how much RAM VBox is actually taking from the OS to run them. Likewise disk usage- 8GB+ for every VM (Python Task) that is running isn't good either.



Edit-

boinc_cages_IL_2727241_31732_0 uses 30.5MB of RAM.

As reported by Windows Task Manager? What about the Virtual Box files that are running (i think there are 3 of them- VirtualBox Manager, VirtualBox Interface, VirtualBox Global Interface) How much RAM are they using?

---

Grant
Darwin NT

I wondered where TACC got their BOINC stuff.

TACC simply gives you an access to their hw (and some implementation support).
But the code is up to you.
They also have a native boinc project, that gives an interface from HPC to volunteers client

It might be time to say goodbye to RAH.I've been grinding a long time for them, its a shame to leave.

It's a pity....

---

Yeah, you're right, I need way more ram.

Python tasks need like what? 6Gib of RAM each?

Maybe...
I'm thinking that's what they insist on to start, and so VBox will take it from the OS and reserve it for that Task. But from the looks of several of your completed Python Tasks, their actual RAM usage is less than 100MB. So in theory, it should be possible for many of them to run at the same time.
VBox reserves 8GB for one Task, it doesn't need it all so when the next Task tries to start, it only needs to pull another 100MB from the OS for two Tasks to be running, with 8GB still available between them. Another Task starts up, only another 100MB is needed from the OS, etc, etc. (Of course i haven't the slightest idea if that's how VBox actually works).

What each Task does require (according to your completed Tasks), is 7.5GB+ of storage space. It looks like each Task needs it's own copy of the VM image in order to run (i'm wondering if this is a repeat of the previous issue with Rosetta 4.xx Tasks when they ran copying all the support files every time a new one started & then deleting them when done instead of just linking to them, or if it's a issue with how VirtualBox works).

I've given BOINC 280GB of free disc space. I'll check the actual ram usage of VB Python tasks, it's not that high IIRC

Thanks for that.
While each Task doesn't use much RAM in it's Virtual Machine, i'm curious as to how much RAM VBox is actually taking from the OS to run them. Likewise disk usage- 8GB+ for every VM (Python Task) that is running isn't good either.



Edit-

boinc_cages_IL_2727241_31732_0 uses 30.5MB of RAM.

As reported by Windows Task Manager? What about the Virtual Box files that are running (i think there are 3 of them- VirtualBox Manager, VirtualBox Interface, VirtualBox Global Interface) How much RAM are they using?

According to task manager, for that specific task, it's around 30MB for the VirtualBox Headless Frontend, 3.0MB for the VirtualBox Interface, 0.1MB for the VirtualBox Global Interface, and 0.1-1MB for two more instances of the VirtualBox Headless Frontend that I don't know the purpose of. In total, it's 35MB, give or take. I'll take a look at some other tasks once this one completes. That task is taking a really long time to run, but it appears to be actually running.

Yes, It's sub-optimal that each task takes around 8 GiB of storage to run. However, I don't think it's possible for them to share storage like the improved Rosetta 4.20. Not even LHC does that, and they should be one of the best vBox projects on BOINC. Since the base memory of the VMs are 6144MB, I'm assuming they insist on having 6GB of free RAM to run. Perhaps someone well-versed in vBox tasks can chime in?

I could plug in a 2TB hard drive just for BOINC like a crazy person (I have a 1TB HDD idling in my system, but I don't want to use that since it's really, really old), but increasing the RAM is not within my budget. Because of that, I really wish they make the RAM requirements more sane. Why make the RAM requirements 6GB if the vast majority of tasks don't appear to take over 1GB of RAM?

Thank you. I feel a bit stupid - on the same page!

According to task manager, for that specific task, it's around 30MB for the VirtualBox Headless Frontend, 3.0MB for the VirtualBox Interface, 0.1MB for the VirtualBox Global Interface, and 0.1-1MB for two more instances of the VirtualBox Headless Frontend that I don't know the purpose of. In total, it's 35MB, give or take.

Just a bit less than 7.5GB.

Yes, It's sub-optimal that each task takes around 8 GiB of storage to run. However, I don't think it's possible for them to share storage like the improved Rosetta 4.20. Not even LHC does that, and they should be one of the best vBox projects on BOINC. Since the base memory of the VMs are 6144MB, I'm assuming they insist on having 6GB of free RAM to run. Perhaps someone well-versed in vBox tasks can chime in?

Not using the same disk image is probably related to security.
But if the Tasks and VBox itself are only using less than 1GB of RAM (which they appear to be well under), then allowing BOINC to use 8GB of storage per Task being processed should allow more than 1 Task to run on a system with plenty of cores/threads if it's given access to that extra storage.
Have any extra Python Tasks started up with the extra storage space made available?

Why make the RAM requirements 6GB if the vast majority of tasks don't appear to take over 1GB of RAM?

Agreed.
From what i've been able to find online generally is that VirtualBox itself needs 500MB, and if the Tasks are all using less than 100MB, then there's no need to put 7.5GB RAM as a minimum requirement.

If a few more people that have got Python Tasks running, particularly those with 2 or more at the same time, could let us know just how much RAM is being used in total for all the running Python Tasks, and how much storage space is being used, we might be able to point it out to the Project and get the minimum requirements changed to something more realistic, letting people get more work done instead of having cores/threads sitting idle while doing just a single Python Task or two.

---

Grant
Darwin NT

Have any extra Python Tasks started up with the extra storage space made available?

All the tasks got downloaded when there was at least 280GB of free disc space. Still, only one runs at a time with all the other ones waiting. Sometimes, BOINC will pause a task to start a new one.

Occasionally, BOINC will pause a task to download a new one and run that, even if said task is close to the deadline, but that's besides the point.

I just realized Rosetta is eating up 20GB of storage. Yikes, that's...bad... I just let BOINC have my entire 2TB media hard drive sans 250GB since I cannot possibly fill it up. In my case, that's a tad over 300 GB. I've never been able to get more than one python task running simultaneously. I'm not short on storage, I'm short on memo...what was I sayin'?

I've never been able to get more than one python task running simultaneously.

Are you sure you have set the CPU(s) usage to 100%, in 'Processing preferences'?

You are running the Pythons so it makes sense that most of Pythons are waiting to run.
However, with 16 GB of memory, you should be able to run 2 Pythons.
At least, my Ryzen 1400 can run 2 pythons with 16 GB.

---

From what I have seen running here @home, it is the insane amount of memory [7.45GB in task/properties] the RPP tasks demand that stops us from running them
I have lots of disk space, they download ok, on a 32GB system 16 cpu, it usualy runs three, once it ran fore for a while,
{in BM memory is set to use 99% when active, 100% when idle}
then I think BM kacked it, and sent the forth into `waiting` probably coz I was now active/using the system, checking to see what these &*$"@:~ python tasks where doing
If the Admin can get the massive memory demand down then they will get a lot more RPP done
But `we` know it, and we , here on the forum just want them to RTFM [forum actualy] :)
Then they will know why all the RPP are clogging up the que.

Now that I have written this pointless post I will go and rehabilitate by banging my head on the wall , and scream at a lump of rock . . . . .