You say that you *can’t* use app_config to limit the number of work units but I’ve been doing so for a couple of years with zero problems.

If you check out several of the other threads that Greg_BE has posted to, you would see that using max_concurrent has caused huge amounts of problems in the past- basically the Scheduler allocates 100s (or more) Tasks, when only a few are actually needed.
While it might not cause problems with your systems & projects, it does with Gre_BE here at Rosetta on one of his systems.
As jim1348 posted, he has also had similar issues, when using project_max_concurrent.

There is a bug (rare as it is) with max_concurrent/project_max_concurrent that has yet to be resolved.

OK, that is useful. It may happen only when running multiple work units (or at least more than two).
In that case, smaller memory may be better. You can't use an app_config to limit the number of work units until they get the download bug fixed.

I can run Rosetta in a second BOINC instance and limit it to one or two work units at a time, but that affects both the pythons and the non-pythons.
They need to give us some way to select them.

Thanks.

Hi, I am running Rosetta@Home on two computers, one 2016 MacBook Pro, and one PC Laptop purchased and set up last year. My Macbook has been downloading and running tasks successfully, however, my PC has never downloaded any Rosetta@Home or Ralph@home tasks. I am not sure why this is, or how to fix it, and would appreciate any support that could be offered.

And how can CPU's be "slowed" if each core is doing its own thing?
All RAH tasks have their own cores as do the other projects.
The GPU stuff has it own core to monitor its work and one core is free for system and web.
So what exactly is "slowing" things down?

Bryn Mawr - added the half_life, will sit back and see what happens.
Current WCG is dying in credits, guess I will have to pump that one up higher in %

Or just let things be until they have a chance to settle down- with 8 active projects, even with the changed half life value, i'd expect you're looking at a couple of weeks. One week bare minimum.
Then adjust Resource share as necessary.

Ok..will do.
It's 5 active.
I thought I had 2 GPU projects, but it seems just one at the moment.
So its 3-4 CPU projects.

I recently (6 weeks ago) added a 5th project (6 if you include Ralph which very rarely has work) because 3 of the projects were out of work / broken at the same time.

One of my crunchers is now back to running smoothly whilst the other still has the occasional lump or bump as one project or another grabs a bit extra but is almost there.

I had more than a lump and a bump before I tried dividing up the computer.
Like now, WCG is really really down close to dead and now that I opened things back up it still is down, but the results I checked are pending. So there is hope.

Bryn Mawr - added the half_life, will sit back and see what happens.
Current WCG is dying in credits, guess I will have to pump that one up higher in %

Or just let things be until they have a chance to settle down- with 8 active projects, even with the changed half life value, i'd expect you're looking at a couple of weeks. One week bare minimum.
Then adjust Resource share as necessary.

Ok..will do.
It's 5 active.
I thought I had 2 GPU projects, but it seems just one at the moment.
So its 3-4 CPU projects.

Initially I left things alone and then credits got all out of whack, then I ran into issues with tasks taking up days on end and nothing else getting done by other projects and just a bunch of yoyo stuff going on.
So I took back control. Again, everything was working fine until this bug showed up. And that just showed up. Maybe after updating to the latest BOINC.

Anyway..I'll mess around with things until I find the right mix.
No need to clog up this thread.

Hopefully they don't switch exclusively to vbox - or give users the ability to choose workunit types. There are doubtlessly countless machines that do not have virtual box installed and likely will not do so as they simply sit and crunch with users not checking the forums.

How much memory does each WU consume with these new python WUs? Do they finally use SSE/Avx? I don't think I have gotten one yet.
thanks

I doubt we'll be out of normal Rosetta units for a while yet because I believe the Robetta server takes requests in from around the world and distributes them on r@h. I wouldn't expect all those users to start using trrosetta yet, but I might well be wrong. Would be good to hear from someone in the project.

I'm not a lucky man....

<error_code>-119 (md5 checksum failed for file)</error_code>
<error_message>MD5 check failed</error_message>

Would you please include a link to one of the tasks that is causing this?

Do you have any other work from Rosetta?

Here is a crazy idea, set the project to 'no new tasks'. Finish all the non python work you have and then click on reset the project button. All I am thinking here is that it will maybe randomly reattach at a better point in the server queue. It is not a real fix to the problem, but it will take you back to a clean state.

Also just for the heck of it, be sure that you have the latest VM and extension pack. Again, may or may not help with the problem, but its worth a try.

Oh well, a few more hours & i'll be out of work again, even though this time there's still millions available.

I don't want to jinx things, but work appears to be flowing again.
Complains about the lack of VirtualBox messages keep occurring, but at least i can get work again.

I was making a comparison between Rosetta and other projects I participated in.

It would be better if the credit system were on a level playing field.

S. Gaber

So it takes 8 hours to complete one R@H task. BOINC sent me 16 tasks, all with the same deadline, three days hence on Septmber 17, 2021. There are only 72 hours in those thre days. Right now I have 15 uncompleted tasks, at 8 hours each, totalling 120 hours to complete. Ain't gonna happen. I could do it in maybe 5 days.


Which means that Boinc has supplied exactly the number of tasks that your machine could do in 3 days - 72 hours on each of 2 processors = 144 hours capacity.

That would be true if I didn't have three other projects to run. If I do all of those Rosetta tasks on time, my other projects would suffer.

What I don’t understand is why you stop the project for the interim rather than just leave it be.

I stop the download of the R@H work 'cause i don't like to have mixed different project wu's on my pc.
So i'm crunching other projects until Rosetta's return

Add TN-Grid alongside (as I have done) but why switch and stop Rosetta?

Usually, the "no-wus status" is, at minimum, from 4 days.
I'll return when wus are on the road....

And we're out of work again,

Switch to TN-Grid

I know that the tech guru of RAH left some years ago, but honestly, now this has become a real hit and miss project. With all the big banner logos on the home page you would think they would have someone on call to fix these kind of things.

How long have we been "dry" now? A few days and no news?
Insane.
I've been around since 2006 and ever since the "Guru" left, this projects attention to technical details has gone down and the silence out of the group is deafening.

Most of now just shrug and let our other projects take over, but this has always been my top project. Now I am beginning to think less of it due to these issues.

This is probably an issue for the BOINC board, but since I know you jamokes I will ask here first.

On one of my hosts, the BOINC manager will not launch. I try to run it as I have in the past, but nothing happens at all.

The host seems to be processing work, based on the CPU usage. But no joy with the manager program.

Any suggestions? I suppose that I can uninstall/reinstall; will that disturb anything?