Rosetta workloads are far bigger than for Instance Seti.
The Workload that was downloaded took up more space as I reserved for Boinc, so it blocked all other incoming packages!

Also, the workloads I get are only valid for a week and each package takes more than 8 hours of calculation. This is completely unrealistic.

Seti offers an 8-week timespan for a 2h workload.
In Comparison Rosetta would need to extend their period by adding 15-times the amount of time for the load to be finished.

The project just deleted over 40hours of work done, due to the limited timespan until the deadline.

So not only is Rosetta blocking other projects by exceeding the disk-quota, it is also a pure waste of my CPU if I get unrealistic deadlines.

Would have loved to support,
but if every item I receive goes to another PC once I'm 80% finished, it is no use to participate at all.

No offense, I might try again some time
Best Regards
Robin

This appears to be happening again. I got a FLOOD of Rosetta tasks that clearly ignores my preference settings and have a deadline date insanely to short to allow completion. Perhaps Rosetta is assuming 100% of my workstation/processor is dedicated to this one project, again ignoring my preferences.
I just was forced to abort all the pending jobs and overdue tasks. A huge waste of processing time.
I've set the project to accept no new tasks until I see an update that they have fixed this.

Sorry, but if the project is going to keep doing this I'll have to leave the project permanently.

Rosetta workloads are far bigger than for Instance Seti.
The Workload that was downloaded took up more space as I reserved for Boinc, so it blocked all other incoming packages!

Also, the workloads I get are only valid for a week and each package takes more than 8 hours of calculation. This is completely unrealistic.

This appears to be happening again. I got a FLOOD of Rosetta tasks that clearly ignores my preference settings and have a deadline date insanely to short to allow completion. Perhaps Rosetta is assuming 100% of my workstation/processor is dedicated to this one project, again ignoring my preferences.
I just was forced to abort all the pending jobs and overdue tasks. A huge waste of processing time.
I've set the project to accept no new tasks until I see an update that they have fixed this.

Sorry, but if the project is going to keep doing this I'll have to leave the project permanently.

Rosetta workloads are far bigger than for Instance Seti.
The Workload that was downloaded took up more space as I reserved for Boinc, so it blocked all other incoming packages!

Also, the workloads I get are only valid for a week and each package takes more than 8 hours of calculation. This is completely unrealistic.

You say Rosetta completely ignores your settings, but it's the Boinc Manager itself that's responsible for scheduling tasks.

Can you tell us what your Boinc settings are? Sometimes they seem a bit counter-intuitive.

What resource share do you use for each of your projects?
Under the "Computing Preferences" menu, on the Computing tab, in the section entitled Other, what settings are you using?
Under the Disk & settings tab, what settings are you using?
Is your computer on 24/7 or just limited hours each day?

---

Seti@Home:
Final data is in the splitter queue.
As promised, we've stopped the process that puts new data into the queue

I thought I would try Rosetta once again.
Actually it got worse than better.
Just downloaded the first Package and it has a deadline on Apr 13.
So if a week wasn't enough, let's try with 3 days!!

Since I downloaded it, I will keep this task alive.
But I already set BOINC to not download another package.
Created Screenshots of all Settings but I cannot upload to this Forum and I've got no WebSpace to put the images :-/

Curious if I will able to complete the package in time. There is a 97% chance that I will not, due to the normal usage of the mac.
Best Regards

Seti@Home:
Final data is in the splitter queue.
As promised, we've stopped the process that puts new data into the queue

I thought I would try Rosetta once again.
Actually it got worse than better.
Just downloaded the first Package and it has a deadline on Apr 13.
So if a week wasn't enough, let's try with 3 days!!

Why wouldn't 3 days be enough? The default Target CPU run time is 8 hours.

Curious if I will able to complete the package in time. There is a 97% chance that I will not, due to the normal usage of the mac.

Why would normal usage not make it possible to complete the task?
Or do you have BOINC set to suspend work while the computer is in use? Is there a particular programme that is impacted by crunching? If so, you can set BOINC to stop crunching when that programm is in use, but keep working the rest of the time.
My system uses all cores & threads all the time with no impact on other programmes or system responsiveness.


Just like Seti, and all other projects, it takes time for the Manager to get the Estimated processing time to match the actual time. With the longer running Tasks, it does take longer for them to adjust. And it's best to run with a small cache to avoid getting more work than you can handle when applications change or you get dodgy Tasks.


These are settings i am using with no effect on system performance or responsiveness, and cache settings being met with no deadline issues.
6c/12t & 32GB RAM

Computing
   Usage limits	
                                   Use at most 100% of the CPUs
                                   Use at most 100% of CPU time

   When to suspend	
           Suspend when computer is on battery (not selected)
               Suspend when computer is in use (not selected)
 Suspend GPU computing when computer is in use (not selected)
   'In use' means mouse/keyboard input in last 3 minutes
  Suspend when no mouse/keyboard input in last --- minutes
     Suspend when non-BOINC CPU usage is above --- %
                          Compute only between ---

   Other	
                                Store at least 1 days of work
                     Store up to an additional 0.02 days of work
                    Switch between tasks every 60 minutes
     Request tasks to checkpoint at most every 60 seconds

   Disk
                              Use no more than 20 GB
                                Leave at least 2 GB free
                              Use no more than 60 % of total

   Memory
          When computer is in use, use at most 95 %
      When computer is not in use, use at most 95 %
 Leave non-GPU tasks in memory while suspended (not selected)
                   Page/swap file: use at most 75 %

---

Grant
Darwin NT

Why wouldn't 3 days be enough? The default Target CPU run time is 8 hours.

Well then we have a different idea about the BOINC project.
Maybe you should rename the project to -> "Rosetta@dedicated_PC_with_no_other_tasks_running" instead of "Rosetta@Home" where people are encouraged to use spare CPU cycles on their HomeComputers.

.. do you have BOINC set to suspend work while the computer is in use?

Yes, and this was never an issue and I completed far more than 90% of SETI@home and Asteroids@home.
climateprediction.net had the same issue with deadlines, but they don't put @Home in their name.

Is there a particular programme that is impacted by crunching? If so, you can set BOINC to stop crunching when that programm is in use, but keep working the rest of the time.
My system uses all cores & threads all the time with no impact on other programmes or system responsiveness.

Fusion360, SketchUp, Blender are all affected when BOINC takes all cores.

Just like Seti, and all other projects, it takes time for the Manager to get the Estimated processing time to match the actual time. With the longer running Tasks, it does take longer for them to adjust. And it's best to run with a small cache to avoid getting more work than you can handle when applications change or you get dodgy Tasks.

I would love to see the statistics how many packages need to be shipped to clients more than once!
And I guess you would have more throughput if you'd just extend the deadline.

Honestly, on machines that crunch 24/7 a longer deadline does not harm anyone at all.
On "SinglePC-Owners"-side, you could gain more results without having to ship the packages again.

Computing
   Usage limits	
        Use at most 75% of the CPUs
        Use at most 80% of CPU time -> to keep 'snappyness'

   When to suspend	
        Suspend when computer is on battery (selected)
        Suspend when computer is in use (not selected)
        Suspend GPU computing when computer is in use (not selected)
        'In use' means mouse/keyboard input in last 1 minutes
        Suspend when no mouse/keyboard input in last --- minutes
        Suspend when non-BOINC CPU usage is above 60 %
        Compute only between ---

   Other	
        Store at least 1 days of work
        Store up to an additional 1 days of work
        Switch between tasks every 60 minutes
        Request tasks to checkpoint at most every 30 seconds

   Disk
        Use no more than 5 GB
        Leave at least 50 GB free
        Use no more than 10 % of total

   Memory
        When computer is in use, use at most 50 %
        When computer is not in use, use at most 90 %
        Leave non-GPU tasks in memory while suspended (selected)
        Page/swap file: use at most 50 %

Best Regards

I'm guessing that "normal usage" was meant to be a reference to the number of hours per day the machine is powered on.

---

Rosetta Moderator: Mod.Sense

This is a very interesting subject/discussion, especially atm

Why wouldn't 3 days be enough? The default Target CPU run time is 8 hours.

Well then we have a different idea about the BOINC project.

Boinc isn't a project, it's a platform. What you mean is Rosetta is a very different project from Seti. And you'd be 100% right.
One of the reasons Seti is on hiatus atm is their tasks still haven't been evaluated yet aiui. There was a (longer) deadline but no real priority.
While at Rosetta, the results are evaluated after 2-3 days (even from before the deadline) and the results can be used to adapt the next batch of tasks, which will also only have another 3 day deadline. And that's because it's running COVID19 tasks, so the urgency is obvious

So when you say

Honestly, on machines that crunch 24/7 a longer deadline does not harm anyone at all.

That is most certainly not true at all. Rosetta is not Seti and the assumptions you could reasonably make about Seti don't apply here.

Maybe you should rename the project to -> "Rosetta@dedicated_PC_with_no_other_tasks_running" instead of "Rosetta@Home" where people are encouraged to use spare CPU cycles on their HomeComputers.

.. do you have BOINC set to suspend work while the computer is in use?

Yes, and this was never an issue and I completed far more than 90% of SETI@home and Asteroids@home.
climateprediction.net had the same issue with deadlines, but they don't put @Home in their name.

With Seti at an end, you aren't running any other Boinc tasks than Rosetta. And you've put in a setting that stops all Boinc tasks when you're running non-Boinc tasks, so there's no new issue here.

Is there a particular programme that is impacted by crunching? If so, you can set BOINC to stop crunching when that program is in use, but keep working the rest of the time.
My system uses all cores & threads all the time with no impact on other programmes or system responsiveness.

Fusion360, SketchUp, Blender are all affected when BOINC takes all cores.

Ok, these seem to be high processor intensive programs that I assume you run 24/7 too, which will be the cause of so little processing time going to Boinc tasks and explains why 8hr tasks struggle to complete over their 72hr deadline. If those are your priority, that's entirely for you to decide.

The issue isn't that Rosetta tasks are processor intensive, but that your other programs are processor intensive and you don't want any Boinc task to have any priority over them at all that might extend their runtime. Again, entirely for you to decide.

I'd like to make some suggestions to your settings that might help

Computing
   Usage limits	
        Use at most 75% of the CPUs
        Use at most 80% of CPU time -> to keep 'snappyness'

Use at most 50% of CPUs (actually cores) so that only 4 of your 8 cores are running at one time and the other 4 are running 0% ever so that other programs have twice as much processor time to work with
Use at most 100% of CPU time. Counter-intuitively, anything less than 100% makes processing less snappy. And note, this only applies when other tasks require less than 60% of the processor (see later)
Combined, this is 50% of your PC rather than 60%, and only 4 cores will run at a time rather than a slightly flaky 6 cores, while also reducing the memory and disk space req'ts of 6 tasks at a time to just 4

        Suspend when non-BOINC CPU usage is above 60 %

Keep this, if you prefer, but it's almost like you don't want Rosetta to run at all. If your other programs are running it sounds like you don't want any degradation in their output, but something's got to give, surely?

   Other	
        Store at least 1 days of work
        Store up to an additional 1 days of work
        Switch between tasks every 60 minutes
        Request tasks to checkpoint at most every 30 seconds

You don't like tasks coming down that will be wasted, but this is much more than Boinc defaults, only making matters worse, both in disk space and the possibility that tasks will be held in memory, so:
Store at least 0.2 days work
Store 0 additional days
Switch between tasks every 999 minutes
Checkpoint every 120 seconds
The first two, less disk space, the third less RAM, the last less disk access. All will fall more easily into the Disk and RAM settings you're already ok with and allow

Everything else can stay the same. See how you get on and report back.
It may not solve everything (or even anything tbh) but the goal is to contribute as much as you can (in your spare CPU time, which it seems you have very little of) while falling within the turnaround times Rosetta demands

---

.. do you have BOINC set to suspend work while the computer is in use?

Yes, and this was never an issue and I completed far more than 90% of SETI@home and Asteroids@home.

And if you had spent much time in the forums you would know just how many people were pointing out how ridiculously long the deadlines were, for tasks that completed in a few hours (or even minutes) even allowing for the slowest supported, rarely on & rarely computing, systems.

Fusion360, SketchUp, Blender are all affected when BOINC takes all cores.

In the BOINC Manager, Options, Exclusive applications allows you to select specific applications so that when they run, BOINC will suspend.
That way you can use all cores & threads, 100% of the time and even with "Suspend when non-BOINC CPU usage is above xx%" left blank with no impact on other applications.
You could also use app_config.xmlto limit the number of cores/threads Rosetta uses.

As SId mentioned, having "Use at most 80% of CPU time" set to anything other than 100% actually reduces system responsiveness.

Or you could go to your account, Rosetta@home preferences and change the Target CPU run time to 4 hours. Still the same deadline, but only half the processing time required to complete a Task.

Honestly, on machines that crunch 24/7 a longer deadline does not harm anyone at all.

Unless the data is time critical. In Seti it wasn't, whereas here sooner is better.

---

Grant
Darwin NT

Fusion360, SketchUp, Blender are all affected when BOINC takes all cores.

In the BOINC Manager, Options, Exclusive applications allows you to select specific applications so that when they run, BOINC will suspend.
That way you can use all cores & threads, 100% of the time and even with "Suspend when non-BOINC CPU usage is above xx%" left blank with no impact on other applications.
You could also use app_config.xml to limit the number of cores/threads Rosetta uses.

Not a bad idea. I was trying to see if Rosetta could co-exist with them first, but your idea makes double sure, maybe at the cost of some running time.

Or you could go to your account, Rosetta@home preferences and change the Target CPU run time to 4 hours. Still the same deadline, but only half the processing time required to complete a Task.

Another choice I was holding back from. Depends how successful the other changes were before entering that territory

---

I've been running Rosetta@home since 03/04/2020 after the demise of seti@home.

I have not completed any work yet. My Stats graph is a horizontal line.

I have tasks downloading & tasks running. Then nothing. I feel like I'm wasting my time & yours.

What am I doing wrong? I ran seti@home for over 20 years with no problems.

---

I have tasks downloading & tasks running. Then nothing.

Your computer shows 3 Tasks as still in progress. Do they show in the BOINC Manager Tasks tab as Running? Progress is more than 0%?

What am I doing wrong?

No idea. There is no indication of the computer you are using here having ever been used at Set, so i can't see how it did over there. Did you make a new account to connect to Rosetta?

In your Rosetta account page, Computing preferences, how do your selections compare to these?
The ones that will have the biggest impact are the CPU ones if set to less than 100%, and if the computer is set to suspend at all.

Computing
   Usage limits	
                                   Use at most 100% of the CPUs
                                   Use at most 100% of CPU time

   When to suspend	
           Suspend when computer is on battery (not selected)
               Suspend when computer is in use (not selected)
 Suspend GPU computing when computer is in use (not selected)
   'In use' means mouse/keyboard input in last 3 minutes
  Suspend when no mouse/keyboard input in last --- minutes
     Suspend when non-BOINC CPU usage is above --- %
                          Compute only between ---

   Other	
                                Store at least 1 days of work
                     Store up to an additional 0.02 days of work
                    Switch between tasks every 60 minutes
     Request tasks to checkpoint at most every 60 seconds

   Disk
                              Use no more than 20 GB
                                Leave at least 2 GB free
                              Use no more than 60 % of total

   Memory
          When computer is in use, use at most 95 %
      When computer is not in use, use at most 95 %
 Leave non-GPU tasks in memory while suspended (not selected)
                   Page/swap file: use at most 75 %

---

Grant
Darwin NT

Why wouldn't 3 days be enough? The default Target CPU run time is 8 hours.

Well then we have a different idea about the BOINC project.
Maybe you should rename the project to -> "Rosetta@dedicated_PC_with_no_other_tasks_running" instead of "Rosetta@Home" where people are encouraged to use spare CPU cycles on their HomeComputers.

I'm dealing with the same frustration. When I first started this I would let my computer run all night long. I'd have to to get these insanely long 8 hour tasks complete. My problem is that my computer is in my bedroom and I am tired of the lights and the fans running while I am sleeping. My computer is on for 4 - 5 hours per day now and I let BOINC run while I surf the web. Now it's taking 2 or 3 days to complete Rosetta tasks so I just deleted Rosetta and the only task that runs is World Community Grid. More than half of those tasks are OpenPandemics and they complete in 1-2 hours.
Sorry Rosetta but your tasks take too long to continue running.

Why wouldn't 3 days be enough? The default Target CPU run time is 8 hours.

Well then we have a different idea about the BOINC project.
Maybe you should rename the project to -> "Rosetta@dedicated_PC_with_no_other_tasks_running" instead of "Rosetta@Home" where people are encouraged to use spare CPU cycles on their Home Computers.

I'm dealing with the same frustration. When I first started this I would let my computer run all night long. I'd have to get these insanely long 8 hour tasks complete. My problem is that my computer is in my bedroom and I am tired of the lights and the fans running while I am sleeping. My computer is on for 4-5 hours per day now and I let BOINC run while I surf the web. Now it's taking 2 or 3 days to complete Rosetta tasks so I just deleted Rosetta and the only task that runs is World Community Grid. More than half of those tasks are OpenPandemics and they complete in 1-2 hours.
Sorry Rosetta but your tasks take too long to continue running.

It's amazing how people get excited about joining this project and seem determined <not> to run it.

Go into Boinc Manager. Select Rosetta and click the Your Account box on the left
On the webpage you arrive at, chose Rosetta@home Preferences, select Edit preferences, and on Target CPU run time select the target runtime you prefer.
If you really do run 4-5hrs per day, 8hrs tasks ought to complete within the 3-day deadline already, so that sounds like an exaggeration. Select 6hrs first and see how that turns out for completing within the deadline.
If it doesn't, drop down to 4hrs, but be aware that it's a compromise between runtime, the usefulness of the results and server hits, so the aim should be to run as close to 8hrs as possible while being successful.

Trying to be successful for yourself and the project ought to be the aim, so it helps to try to achieve that before announcing you're giving up.

---