...bumping runtimes further to 12hrs will quadruple your credits compared to that of the faulty default setting

Not wanting to mislead anyone, I wrote that wrong
Credits per Rosetta Beta v6.06 task will quadruple. Credits per hour of CPU runtime will be about the same.

Point being, Rosetta Beta v6.06 tasks set to a target time of:
- Not selected: runs for 3hrs and you get 3hrs worth of credit - even though Boinc initially says they'll run for 8hrs
- 8 hours: runs for 8hrs and you get 8hrs worth of credit
- 12 hours: runs for 12hrs and you get 12hrs worth of credit - even though Boinc initially says they'll run for 8hrs

This doesn't apply to Rosetta v4.20 tasks you may occasionally see, where:
- Not selected: runs for 8hrs and you get 8hrs worth of credit

8hrs is the ideal as you get the intended Rosetta default runtime and credit (instead of falling short every time), doesn't 'waste' our limited remaining queue of tasks and doesn't screw up Boinc's task scheduling.
12hrs (or 10hrs) is an option to get you more credits per task <if you're meeting deadlines comfortably> without messing up Boinc's scheduling too much and further extends how long our limited queue of tasks lasts for.

---

Hello.
Is it possible to cancel RAM limitations for rosetta beta 6.06?
The client on one of my PCs cannot receive WU by issuing the message "Rosetta beta needs 3337.86 MB RAM but only 2301.15 MB is available for use."
At the same time, on my main PC, I see that the RAM consumption of one wu is only about 100 MB.

Hello.
Is it possible to cancel RAM limitations for rosetta beta 6.06?
The client on one of my PCs cannot receive WU by issuing the message "Rosetta beta needs 3337.86 MB RAM but only 2301.15 MB is available for use."
At the same time, on my main PC, I see that the RAM consumption of one wu is only about 100 MB.

I haven't seen tasks asking for that much RAM for a very long time, but back then it was very typical for tasks to require enormous amounts of RAM when they started to run, but never used anywhere close to that amount once they start running, in exactly the way you describe.

The solution was to give Boinc access to a large amount of RAM to get past the initial hurdle, knowing that it wouldn't keep hold of it.

In Boinc Manager, under the Options menu select Computing preferences

On the first tab, Computing
In the section 'When computer is in use' I've set 'Use at most 80% of memory'
In the section 'When computer is not in use' I've set 'Use at most 90% of memory'

If this still isn't enough, you can increase those numbers as much as you like

---

While these numbers are going up and down, we may run out in as few as 2 days or as many as 5

~2 hours ago the front page showed

As of 23 Jul 2025, 23:02:29 UTC [ Scheduler running ]
Total queued jobs: 29,429

If there are any tasks left at all by now, I doubt they'll last for more than an hour so make the most use of your remaining cache.
We've had a really good run these last few months.
Fingers crossed for a resupply before too long.

---