how can i solve this problem. i've running windows xp and an optimized boinc client. i run both seti and rosetta, however, i never see any messages for the rosetta project nor any work units ever being processed. how can i get them both to have equal time? i know that i can set the setiathome process in my task manager, but i never see some rosettaathome (don't know what it's called) process in my task manager. any ideas?

Well you have 50 on the m box and 46 on the other so you have lots of WUs, now does the messages say anything about over committed or EDF? If so then it will run SETI until the WU is not going to miss the deadline. You must have your connect to set to high i recommend 2 or 3 to start....How many Seti WUs do you have??????

---

BOINC Wiki

Exit BOINC completely (file/exit), then relaunch, wait a couple of minutes, copy ALL the messages from the Messages tab and paste them here. I think Jim K is right, you have too large a cache for two projects (maximum would be 7 days, recommended 3 or 4) and therefore instead of swapping the projects every hour, it's going to swap projects every few days to meet your resource share. (EDF, or "earliest deadline first" mode.) Remember that at present a 10-day cache means 10 days for EACH project, if it was running all the time; with a two-week deadline on SETI and 20 days work in cache, it _can't_ guarantee that it'll meet the deadline if you truly don't connect again for 10 days, so it'll do the SETI first...

If this is it, and you want them to swap every switch interval, simply reduce your cache size and wait; the overload of SETI you've already collected will have to be worked down, but then it'll start swapping.

---

Exit BOINC completely (file/exit), then relaunch, wait a couple of minutes, copy ALL the messages from the Messages tab and paste them here. I think Jim K is right, you have too large a cache for two projects (maximum would be 7 days, recommended 3 or 4) and therefore instead of swapping the projects every hour, it's going to swap projects every few days to meet your resource share. (EDF, or "earliest deadline first" mode.) Remember that at present a 10-day cache means 10 days for EACH project, if it was running all the time; with a two-week deadline on SETI and 20 days work in cache, it _can't_ guarantee that it'll meet the deadline if you truly don't connect again for 10 days, so it'll do the SETI first...

If this is it, and you want them to swap every switch interval, simply reduce your cache size and wait; the overload of SETI you've already collected will have to be worked down, but then it'll start swapping.

I have 41 WU in my SETI queue and 50 in my Rosetta queue. What should I set my cache size to? I've had it set at 10 days because of the recent issues with the SETI servers going down so wanted to have units to crunch during outages. Should I shrink it down and if so, how much?

---

deleted post

---

Exit BOINC completely (file/exit), then relaunch, wait a couple of minutes, copy ALL the messages from the Messages tab and paste them here. I think Jim K is right, you have too large a cache for two projects (maximum would be 7 days, recommended 3 or 4) and therefore instead of swapping the projects every hour, it's going to swap projects every few days to meet your resource share. (EDF, or "earliest deadline first" mode.) Remember that at present a 10-day cache means 10 days for EACH project, if it was running all the time; with a two-week deadline on SETI and 20 days work in cache, it _can't_ guarantee that it'll meet the deadline if you truly don't connect again for 10 days, so it'll do the SETI first...

If this is it, and you want them to swap every switch interval, simply reduce your cache size and wait; the overload of SETI you've already collected will have to be worked down, but then it'll start swapping.

I have 41 WU in my SETI queue and 50 in my Rosetta queue. What should I set my cache size to? I've had it set at 10 days because of the recent issues with the SETI servers going down so wanted to have units to crunch during outages. Should I shrink it down and if so, how much?

Here are the messages after a restart. I also changed my SETI network connectivity to 4 days instead of 10.

1/9/2006 1:10:16 PM||Starting BOINC client version 5.3.6 for windows_intelx86
1/9/2006 1:10:16 PM||libcurl/7.14.0 OpenSSL/0.9.8 zlib/1.2.3
1/9/2006 1:10:16 PM||Data directory: C:Program FilesBOINC
1/9/2006 1:10:16 PM||Processor: 1 GenuineIntel Intel(R) Pentium(R) M processor 1.60GHz
1/9/2006 1:10:16 PM||Memory: 1022.92 MB physical, 2.40 GB virtual
1/9/2006 1:10:16 PM||Disk: 74.53 GB total, 64.33 GB free
1/9/2006 1:10:16 PM|rosetta@home|Computer ID: 127830; location: home; project prefs: default
1/9/2006 1:10:16 PM|SETI@home|Computer ID: 1982106; location: work; project prefs: default
1/9/2006 1:10:16 PM||General prefs: from SETI@home (last modified 2006-01-09 13:09:13)
1/9/2006 1:10:16 PM||General prefs: no separate prefs for work; using your defaults
1/9/2006 1:10:16 PM||Remote control not allowed
1/9/2006 1:10:16 PM||Listening on port 31416
1/9/2006 1:10:16 PM|SETI@home|Resuming computation for result 22mr05aa.6856.8689.953400.1.97_0 using setiathome version 418
1/9/2006 1:10:16 PM||Suspending work fetch because computer is overcommitted.
1/9/2006 1:10:16 PM||Using earliest-deadline-first scheduling because computer is overcommitted.

---

I have 41 WU in my SETI queue and 50 in my Rosetta queue. What should I set my cache size to? I've had it set at 10 days because of the recent issues with the SETI servers going down so wanted to have units to crunch during outages. Should I shrink it down and if so, how much?

The "overcommitted" message is saying exactly that, you have too much work, and if it alternates, you'll possibly miss a deadline. (Based on the fact that it assumes you CANNOT connect before ten days is up, so even if the last SETI work was done eleven days from now, it would be another nine before you connect again, which would be past the fourteen...) The "maximum possible" cache to avoid this with two projects is 1/2 the shorter deadline - in other words, 7 days. That's based on what the code says; my personal opinion is that half of _that_, or 3.5 days, would be a better figure, although even 6.5 days _should_ always avoid EDF mode. I run four projects on one box; for me 3.5 is the maximum, but I've found 2 is much more "comfortable".

EDF mode isn't an "error" - it's sometimes called "panic mode", but even that isn't really true. It's just a different way of splitting your resource share, to make sure you don't miss deadlines. It does get confusing though, because you'll work on SETI for days, then on Rosetta for days, and most people prefer to see the alternation happening a lot quicker than that.

---

Here are the messages after a restart. I also changed my SETI network connectivity to 4 days instead of 10.

You will probably take 3-4 days to work the cache down (maybe more); so, you need a little patience ...

Keep an eye on the amount of work and the deadlines. If work is not going to be completed by the deadline (kore likely for SETI@Home) you are likely to be better off just aborting the work.

But, based on what *I* have seen here, you are in EDF mode and until you get the SETI@Home backlog worked down you will not do any )or much) Rosetta work ...

---

Here are the messages after a restart. I also changed my SETI network connectivity to 4 days instead of 10.

You will probably take 3-4 days to work the cache down (maybe more); so, you need a little patience ...

Keep an eye on the amount of work and the deadlines. If work is not going to be completed by the deadline (kore likely for SETI@Home) you are likely to be better off just aborting the work.

But, based on what *I* have seen here, you are in EDF mode and until you get the SETI@Home backlog worked down you will not do any )or much) Rosetta work ...

thanks. this is my first project aside from seti so still trying to get things figured out. will exercise patience and wait to see my rosetta count change in a couple days.

---

Here are the messages after a restart. I also changed my SETI network connectivity to 4 days instead of 10.

You should be fine. I _think_ you'll be out of EDF mode very soon, but theoretically it COULD take about three days, maybe four, before "enough" SETI has been finished to get you there. It all depends on how accurate your DCF is for both projects at the moment. Just don't suspend any projects or play with any debt numbers, or it'll just get worse! :-) Let it run, it'll all solve itself.

---