On 3 of my machines I run Rosetta as well but although I have set computing preferences to switch between tasks every 60 minutes, running Rosetta kills seti@home work.
What am I doing wrong here please?
TIA
George

---

Task swapping does not work the way one might think!
It works on a longish term average effort, so one project, normally the one with the shorter deadline (Rosetta in this case) will dominate for some time, then the other project will get a chance and catch up - and this timescale is several days...

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

On 3 of my machines I run Rosetta as well but although I have set computing preferences to switch between tasks every 60 minutes, running Rosetta kills seti@home work.
What am I doing wrong here please?
TIA
George

what do you mean 'kills' ?

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

"Kills" here means no tasks for SETI@home seem to get done, only Rosetta and my primary interest is SETI@home

---

A-ha! Thanks Bob.

---

In that case I would reduce the resource share for rosetta and make sure I don't carry a large cache - that would prompt boinc to put rosetta with its short ealines at the head of the queue. you can also reduce from rosetta's default 3h (iirc) setting per task to 1h.

with some projects, especially those with almost unlimited WU supplies like Einstein and Rosetta, it can be a bit tricky to get boinc to behace like you want.

As Rob said, eventually it should even out.

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

Yes, it works out in the long term, but DA made the dang thing (BOINC) try and work out it as if each project was attached from the beginning of time. Frustrating for a human to watch and not what most intend.

---

One way to sway things in favour of SETI@Home is to use the "Resource share" setting for the two projects, drop Rosetta to a very low number, say 10 while pushing SETI up to 1000, doing this will give Rosetta a time average work of 1% of SETI (but it can still appear to be a bit of a thug).
Alternatively, if you just want Rosetta to be a reserve project set its share to 0 - it will only get work when there is no work at all coming out from SETI, and you have run out of SETI work in your cache.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

you can try fiddle with the REC decay rate, too.

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

One way to sway things in favour of SETI@Home is to use the "Resource share" setting for the two projects, drop Rosetta to a very low number, say 10 while pushing SETI up to 1000, doing this will give Rosetta a time average work of 1% of SETI (but it can still appear to be a bit of a thug).
Alternatively, if you just want Rosetta to be a reserve project set its share to 0 - it will only get work when there is no work at all coming out from SETI, and you have run out of SETI work in your cache.

Last time I looked Rosetta was still running server code from the dawn of time (2008 or so) that doesn't allow you to set a 0 resource share.

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

One way to sway things in favour of SETI@Home is to use the "Resource share" setting for the two projects, drop Rosetta to a very low number, say 10 while pushing SETI up to 1000, doing this will give Rosetta a time average work of 1% of SETI (but it can still appear to be a bit of a thug).
Alternatively, if you just want Rosetta to be a reserve project set its share to 0 - it will only get work when there is no work at all coming out from SETI, and you have run out of SETI work in your cache.

Last time I looked Rosetta was still running server code from the dawn of time (2008 or so) that doesn't allow you to set a 0 resource share.

However it should accept scientific notation for the resource share, so 1.0e-30 might as well be zero.

---

One way to sway things in favour of SETI@Home is to use the "Resource share" setting for the two projects, drop Rosetta to a very low number, say 10 while pushing SETI up to 1000, doing this will give Rosetta a time average work of 1% of SETI (but it can still appear to be a bit of a thug).
Alternatively, if you just want Rosetta to be a reserve project set its share to 0 - it will only get work when there is no work at all coming out from SETI, and you have run out of SETI work in your cache.

Last time I looked Rosetta was still running server code from the dawn of time (2008 or so) that doesn't allow you to set a 0 resource share.

However it should accept scientific notation for the resource share, so 1.0e-30 might as well be zero.

Resource share
If you participate in multiple BOINC projects, this is the proportion of your resources used by Rosetta@home 1E-11

ROFL. mind you setting a value of 0 put it on 100 :D

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

Rob/William
The evening out seems to be happening now. SETI@average increasing and Rosetta decreasing

---