I have just recently been able to complete and submit a first BOINC wu. This finished 2 days ago and has only just appeared on this site. However it gives me 27.36 credits and an average of 0.08! Not only that but my user account shows about 50 wus pending, and all but the first ten with a deadline of 14 days time. It takes nearly 14 days to complete a BOINC wu. There seems to be no control over how many wus are downloaded, and even less on removing the ones that the client is processing but which will never be finished before the deadline.
Is there some practical way of controlling the client?

---

Check the option on your account, under the option general preferences, there is an option connect to network every x days! It must have a value to high and therefor you have so much workunits pending to be crunched! Set it to every 2 days and there be no problems for you!

Hope this helps!

---

<img src="http://boinc.mundayweb.com/one/stats.php?userID=1331">

<blockquote>Check the option on your account, under the option general preferences, there is an option connect to network every x days! It must have a value to high and therefor you have so much workunits pending to be crunched! Set it to every 2 days and there be no problems for you!</blockquote>

A few of the settings in BOINC aren't very intuitive. That one in particular really should be changed. One would think that the setting for "connect to network every x days" determines how often your computer connects to the network, but it doesn't. It determines how many days are cached. Why it doesn't just say that i'm not sure. Regardless of how many days I set that preference to, my machine still dials in every time it finishes a WU.

Not sure what you mean by 'pending', since your computers are hidden. If they say pending in your results file, then they have been completed and are simply awaiting credit. However, I think you probably mean that you have 50 or so work units that have not even started crunching yet?

Dig

---

<blockquote>
The setting for "connect to network every x days" has nothing to do with how often your computer connects to the network. LOL. It determines how many days are cached. Regardless of how many days I set that preference to, my machine still dials in every time I finish a WU.
</blockquote>


I remember if i am not mistake when i used boinc version 4.19 or an earlier version (I have suspended the project by January and back for crunch in March)! I have the option set to 5 days and the computer only connected when the last work unit were at 90% completed, and then download a new set of WU! Never before! After i upgraded to version to 4.25 i noticed what you say, finishing a WU, immediatelly download a new one to mantain a x day cache!

---

<img src="http://boinc.mundayweb.com/one/stats.php?userID=1331">

<blockquote>I have just recently been able to complete and submit a first BOINC wu. This finished 2 days ago and has only just appeared on this site. However it gives me 27.36 credits and an average of 0.08! Not only that but my user account shows about 50 wus pending, and all but the first ten with a deadline of 14 days time. It takes nearly 14 days to complete a BOINC wu. There seems to be no control over how many wus are downloaded, and even less on removing the ones that the client is processing but which will never be finished before the deadline.
Is there some practical way of controlling the client?</blockquote>
My machine completes a BOINC work unit every two hours, and it isn't the fastest around -- why 14 days?

At least until we figure out why it takes so incredibly long to process one work unit, I'd recommend setting the cache to 0.1 days and aborting all of the work units you have now.

---

Nick, from feedback you recieved on the Questions & Answers board, you know that running Classic and Boinc on the same machine simultaneously will cause you a problem.

I suggest you make the switch to Boinc and shut down Classic, it will be better for your stress levels and for the science we are all here to perform.

Good luck and happy crunching,

Richard

---

<blockquote>Nick, from feedback you recieved on the Questions & Answers board, you know that running Classic and Boinc on the same machine simultaneously will cause you a problem.</blockquote>
That explains a lot.

---

<blockquote><blockquote>Nick, from feedback you recieved on the Questions & Answers board, you know that running Classic and Boinc on the same machine simultaneously will cause you a problem.</blockquote>
That explains a lot.</blockquote>
And he only lets BOINC run very occasionally.

---

Grant
Darwin NT

Something to keep in mind: Only the science applications run at low priority. The BOINC client itself runs at "normal" priority. The benchmarks are performed by BOINC, not the science applications. Therefore when BOINC benchmarks your system, it forces seti classic to stop processing so BOINC is getting 100% of your CPU. This obviously means that BOINC thinks it will get 100% of the CPU (or close to it) all the time but since you are running classic along with it, things break.

As has been said before... there is a simple solution: stop running classic or stop running BOINC. They are not designed to run at the same time so any problems that come up as a result of you doing so are your own fault and should not be blamed on the system or the developers. 14 days is a VERY generous deadline. Even my Pentium 2 350 MHz could return a work unit in about 20 hours. There is absolutely no reason for any computer currently in use to take longer than 14 days to complete a seti work unit. If you can't return a work unit in under 14 days, you are hindering the project more than helping it IMHO. Getting results back within a reasonable amount of time is essential to keeping the database clean and ensuring results can be verified reliably

---

A member of The Knights Who Say NI!
For rankings, history graphs and more, check out:
My BOINC stats site

<blockquote>As has been said before... there is a simple solution: stop running classic or stop running BOINC. They are not designed to run at the same time so any problems that come up as a result of you doing so are your own fault and should not be blamed on the system or the developers.</blockquote>
Well said, Toby... well said.

And here I thought I was going to have to come in here and start hiding posts. ;-)

---

Rob

I made my connection every 10 days also the 1st time. I had to get rid of a lot of work and start over. What I did for a while and for people that don't have super computers or who "don't" run there computer 24/7 (like me) might try is this: I first set my connect for .1 days than immediatley after the WU's downloaded I changed it to "0". A zero means you will not get any more WU's. I saw how long it took me to complete the WU's. As I went along (completing WU's) and seeing how long it took me. I slowly increased my connect every "x" days until I found the perfect balance for me. I now have my connect every "x" days set to "1.8" days. This works perfect for me. I get either 1 or 2 WU's everytime I upload a completed WU. Just like most things you have to work out a balance that works for you.

<blockquote>I made my connection every 10 days also the 1st time. I had to get rid of a lot of work and start over. What I did for a while and for people that don't have super computers or who "don't" run there computer 24/7 (like me) might try is this: I first set my connect for .1 days than immediatley after the WU's downloaded I changed it to "0". A zero means you will not get any more WU's. I saw how long it took me to complete the WU's. As I went along (completing WU's) and seeing how long it took me. I slowly increased my connect every "x" days until I found the perfect balance for me. I now have my connect every "x" days set to "1.8" days. This works perfect for me. I get either 1 or 2 WU's everytime I upload a completed WU. Just like most things you have to work out a balance that works for you.</blockquote>
You've definitely got the right idea, Randy. Start with a small cache, and increase it once "things" have more experience.

You don't really need to go back from 0.1 to 0, with a small cache. You won't get anywhere near deadlines, and even on a pretty fast machine it won't get more work until you're nearly done with the current WU.

The other thing is that the scheduler on the server-side will figure out how long it takes for you to return work, and how much your machine runs, etc. and send less work than you request if that makes sense. It'll take them a little time to build the statistics, so 1.8 may be good now, and smaller later.

---