Well , first of all , I\'m new to CPDN. Got my first Model.
I set up everything to my best knowledge, including resource share. Both programs are switching correctly, but it seems, that SETI will empty his queue without downloading new WU\'s.
What is going wrong?

---

If you have a sulfur cycle model it may cause the client to go into EDF mode or no work fetch, due to tighter deadlines. In either case it will adjust by not downloading another CPDN model for some time after it finishes the current one.

---

BOINC WIKI

BOINCing since 2002/12/8

If you have a sulfur cycle model it may cause the client to go into EDF mode or no work fetch, due to tighter deadlines. In either case it will adjust by not downloading another CPDN model for some time after it finishes the current one.

John, you got me wrong. Seti does not download any new WU\'s , although queue is empty. CDPN model\'s due date is August 2006, so there is plenty of time to finish and no need for \"panic mode\" as I see it. Seti and CPDN get both 50% of CPU cycles, but Seti does not fill up it\'s queue again, after it run dry.

---

If you have a sulfur cycle model it may cause the client to go into EDF mode or no work fetch, due to tighter deadlines. In either case it will adjust by not downloading another CPDN model for some time after it finishes the current one.

John, you got me wrong. Seti does not download any new WU\'s , although queue is empty. CDPN model\'s due date is August 2006, so there is plenty of time to finish and no need for \"panic mode\" as I see it. Seti and CPDN get both 50% of CPU cycles, but Seti does not fill up it\'s queue again, after it run dry.

Check your messages tab. If the computer is overcommitted it suspends the work-fetch until it feels there is enough time to complete the work.

I\'ve currently got the following:
18/09/2005 16:03:17||Suspending work fetch because computer is overcommitted.
18/09/2005 16:06:04|rosetta@home|Message from server: No work sent
18/09/2005 16:06:04|rosetta@home|Message from server: (won\'t finish in time) Computer on 77.3% of time, BOINC on 94.3% of that, this project gets 9.1% of that
18/09/2005 16:06:05|rosetta@home|Deferring communication with project for 1 days, 23 hours, 59 minutes, and 59 seconds

Check to see if you get that....if you do you could try increasing the SETI resource share to assign it more time.

---

If you have a sulfur cycle model it may cause the client to go into EDF mode or no work fetch, due to tighter deadlines. In either case it will adjust by not downloading another CPDN model for some time after it finishes the current one.

John, you got me wrong. Seti does not download any new WU\'s , although queue is empty. CDPN model\'s due date is August 2006, so there is plenty of time to finish and no need for \"panic mode\" as I see it. Seti and CPDN get both 50% of CPU cycles, but Seti does not fill up it\'s queue again, after it run dry.

Check your messages tab. If the computer is overcommitted it suspends the work-fetch until it feels there is enough time to complete the work.

I\'ve currently got the following:
18/09/2005 16:03:17||Suspending work fetch because computer is overcommitted.
18/09/2005 16:06:04|rosetta@home|Message from server: No work sent
18/09/2005 16:06:04|rosetta@home|Message from server: (won\'t finish in time) Computer on 77.3% of time, BOINC on 94.3% of that, this project gets 9.1% of that
18/09/2005 16:06:05|rosetta@home|Deferring communication with project for 1 days, 23 hours, 59 minutes, and 59 seconds

Check to see if you get that....if you do you could try increasing the SETI resource share to assign it more time.

Computer was not overcommitted.
Inceasing Seti\'s share did the trick. A ratio of 1:3 seems to work now.
Many thanks for the help

---