I am using Rosetta@Home via Boinc client on Windows and Linux.
I observe that the Expiration date of working units is only 3 days in the future. This is definitly not enough.

My machine should work 24/7 to do all WUs in that time periode.

Another problem is that WUs waiting in the scheduler that still expired the Expiration date will still processed. But in my understanding they should be thrown away because they expired.

btw: One unit take round about 9 hours on my fastes machine. This is more then one working day.

btw: One unit take round about 9 hours on my fastes machine. This is more then one working day.

There are 24 hours in a day, 8 hours during the average workday.
Set a small cache, 0.2 days & 0.01 additional days.
Even if your system is only on for 5 hours a day, it will still be able to return work within the 3 day deadline.

If it does take you more than 3 days to do 8 hours of work, then Rosetta is not a suitable project for you.

---

Grant
Darwin NT

the Expiration date of working units is only 3 days in the future. This is definitly not enough.

That’s how this project works. The tasks are part of active research: the scientists need the results now to guide ongoing and future work.

WUs waiting in the scheduler that still expired the Expiration date will still processed. But in my understanding they should be thrown away because they expired.

That’s my understanding, too, so I’m not sure what’s going wrong there.

One unit take round about 9 hours on my fastes machine. This is more then one working day.

All tasks have a target runtime of 8 hours by default. (Rosetta tasks perform a variable amount of work in a fixed amount of time; they are not fixed amounts of work that take variable lengths of time to complete.) You can reduce the target runtime in your Rosetta@home preferences: go to Edit preferences, and change Target CPU run time to a value that works better for you.

Also (as Grant mentions): it is very important to set your Computing preferences to ensure that you do not download more tasks than you can complete before their deadline.

I am using Rosetta@Home via Boinc client on Windows and Linux.

Another problem is that WUs waiting in the scheduler that still expired the Expiration date will still processed. But in my understanding they should be thrown away because they expired.

This is because most Projects give you the chance to finish it before the next person the workunit is automatically sent to returns it, IF you finish it first then you will get credit for it but if you do NOT return the workunit before the 3rd person who got the workunit then you will NOT get credit for it even if your crunching is valid.

It's best to adjust your workunit cache to a small enough one that you can finish and get new workunits before the 3 day expiration runs out, most people are in the 0.5 to1.5 day work unit cache.

It's best to adjust your workunit cache to a small enough one that you can finish and get new workunits before the 3 day expiration runs out, most people are in the 0.5 to1.5 day work unit cache.

Now we come closer.

My WU-cache is at "0,5" but Boinc still load 4 WUs. 2 are active, the other 2 are waiting.

So it looks like that the decicion what "one day" is, is based on not enough informations. Maybe just my hardware specs are used for calculation and not my real workload/uptime/cpu-usage.

Just for an experiment I set the WU-cache to "0,1" now.

There are 2 values for the cache.

           Store at least xx days of work
Store up to an additional xx days of work

Set "At least " to 0.5 (or less), and "Additional days" to 0.01.
Don't abort work, let the Manger sort things out over a week or so.

---

Grant
Darwin NT

My WU-cache is at "0,5" but Boinc still load 4 WUs. 2 are active, the other 2 are waiting.

Sounds exactly right. At the default setting, one task is 8 hours = 0.33 days. So when you ask to download at least 0.5 days’ worth of work, you’re going to get two sets of tasks: one to run now (which will take less than 0.5 days), and one to run when they’re finished (which takes you to more than 0.5 days).

The client should take the real up- and down-time of the machine into account.

The client should take the real up- and down-time of the machine into account.

It does.
In your account, "Computers on this account", View. Click on any Details for any of you computers and that information is there (it is only viewable by you).

These are those details for my computers.

                                           Fraction of time BOINC is running 99.99%
While BOINC is running, fraction of time computer has an Internet connection 100.00%
               While BOINC is running, fraction of time computing is allowed 100.00%
           While is BOINC running, fraction of time GPU computing is allowed 100.00%

                                           Fraction of time BOINC is running 99.97%
While BOINC is running, fraction of time computer has an Internet connection 100.00%
               While BOINC is running, fraction of time computing is allowed 100.00%
           While is BOINC running, fraction of time GPU computing is allowed 100.00%

---

Grant
Darwin NT

I am using Rosetta@Home via Boinc client on Windows and Linux.
I observe that the Expiration date of working units is only 3 days in the future. This is definitly not enough.

My machine should work 24/7 to do all WUs in that time periode.

Another problem is that WUs waiting in the scheduler that still expired the Expiration date will still processed. But in my understanding they should be thrown away because they expired.

Workunits that are abortd by you OR by the Project because you didn't finish them by the deadline are automatically put back into the queue of available workunits for some other user to crunch.

The problem still exists.

Currently it is Jun 21th 22:38 and one of my two Rosetta WUs are expired Jun 20th 21.02 (25h in the past) but still workes on my CPU wasting ressources, money, CO2 and CPU time for other projects.

I need to turn of Rosetta.

---

I need to turn of Rosetta.

Agreed. If you are not going to bother processing any of the work then there is no point in you downloading any in the first place.
Just select Rosetta on the project page, then Remove.

---

Grant
Darwin NT

The problem still exists.

Currently it is Jun 21th 22:38 and one of my two Rosetta WUs are expired Jun 20th 21.02 (25h in the past) but still workes on my CPU wasting ressources, money, CO2 and CPU time for other projects.

I need to turn of Rosetta.

Just abort it and it will be sent to the 'workunits available' cache for someone else to crunch. It's 3 days for YOU, the next person gets their own 3 days.