I guess people just don't want to tell you the bad news, which is apparently given the way you have chosen to setup BOINC you've never really given it enough run time to complete results regularly within the deadline.

Thought that's what I asked -- how come only 17 hours of crunching a month?

Yes, you two are right. Even with my conservative BOINC settings, I must be away from my computer long enough for the screensaver to turn out a result within the deadline...

Is there a log somewhere to tell me when BOINC ran and for how long?

P.

---

Thought that's what I asked -- how come only 17 hours of crunching a month?

Sorry Ned, I stand corrected! :-)

I guess it was too much of a "kinder, gentler inquiry" that it didn't register at first.

Alinator

I guess people just don't want to tell you the bad news, which is apparently given the way you have chosen to setup BOINC you've never really given it enough run time to complete results regularly within the deadline.

Thought that's what I asked -- how come only 17 hours of crunching a month?

Yes, you two are right. Even with my conservative BOINC settings, I must be away from my computer long enough for the screensaver to turn out a result within the deadline...

Is there a log somewhere to tell me when BOINC ran and for how long?

P.

First things first: SETI classic was a screensaver. BOINC isn't.

Why not just let BOINC run at all times? It will run at the lowest priority and not stop any actual work.

---

Yes, you two are right. Even with my conservative BOINC settings, I must be away from my computer long enough for the screensaver to turn out a result within the deadline...

Is there a log somewhere to tell me when BOINC ran and for how long?

P.

You should be able to see when BOINC suspended and resumed the science apps in the logs at least between sleep intervals and/or shutdowns.

Also the percent run data in your account info might help to estimate the total run time you've had available.

Alinator

I think the most important point here is that Philou seems ( Am I wrong ? )to
believe that letting BOINC run all the time effect his/hers ability
to perform the computers primary function.
BOINC only uses UNUSED clock cycles. You shouldn't even notice a thing.
I burn CD's and all kinds of stuff and never had a problem.

I'd suggest trying (Just for a day) letting the machine run BOINC all the time.
Turn off network access if you like ( I do when not connected to my own home network ).

Give it a shot.

Steve.

---

I think the most important point here is that Philou seems ( Am I wrong ? )to
believe that letting BOINC run all the time effect his/hers ability
to perform the computers primary function.
BOINC only uses UNUSED clock cycles. You shouldn't even notice a thing.
I burn CD's and all kinds of stuff and never had a problem.

I'd suggest trying (Just for a day) letting the machine run BOINC all the time.
Turn off network access if you like ( I do when not connected to my own home network ).

Give it a shot.

Steve.

I think it has to do with the whole classic-as-screensaver concept.

BOINC isn't a screensaver, you can do useful work with BOINC running in the background.

---

I have a similar problem, I have several machienes that are all connected to the internet through a modem and as a few are only on to crunch, i dont check them that often, id like to let them sit for at least 6 or 7 days and then update them but with these new deadlines, i have to check them every 3 or 4

---

I have to agree with Ned! Unlike Seti Classic Seti BOINC is a lot better about "If the user wants to use the computer then wait until they are Done."

I do remember a couple of "Un-Graceful" shutdowns to get my computer back in Classic...

I think the most important point here is that Philou seems ( Am I wrong ? )to
believe that letting BOINC run all the time effect his/hers ability
to perform the computers primary function.
BOINC only uses UNUSED clock cycles. You shouldn't even notice a thing.
I burn CD's and all kinds of stuff and never had a problem.

I'd suggest trying (Just for a day) letting the machine run BOINC all the time.
Turn off network access if you like ( I do when not connected to my own home network ).

Give it a shot.

Steve.

I think it has to do with the whole classic-as-screensaver concept.

BOINC isn't a screensaver, you can do useful work with BOINC running in the background.

---

Please consider a Donation to the Seti Project.

Yes, you two are right. Even with my conservative BOINC settings, I must be away from my computer long enough for the screensaver to turn out a result within the deadline...

Is there a log somewhere to tell me when BOINC ran and for how long?

P.

You should be able to see when BOINC suspended and resumed the science apps in the logs at least between sleep intervals and/or shutdowns.

Also the percent run data in your account info might help to estimate the total run time you've had available.

Alinator

Hi Alinator,
I have found a logfile (stdoutdae.old) in the directory where the BOINC data is kept, and it looks as though BOINC typically runs for pretty exactly two minutes and the quits. I doubt that I have such a good sense of timing that I exit the BOINC screensaver exactly two minutes after it starts, there must be something else at odds? Any ideas?
Many thanks,
Philipp

(BTW I am aware BOINC is not a screensaver, and I also now it's not saving the screen from anything either...)

Excerpts from log file (this is just for one day, but typical for most in the log):

006-05-04 10:39:11 [SETI@home] Resuming computation for result 09au01aa.21558.19025.386086.1.87_1 using setiathome version 418
2006-05-04 10:39:11 [SETI@home] Resuming computation for result 16oc02aa.11249.23297.429814.1.115_1 using setiathome version 418
2006-05-04 10:39:11 [---] Suspending work fetch because computer is overcommitted.
2006-05-04 10:39:11 [---] Using earliest-deadline-first scheduling because computer is overcommitted.
2006-05-04 10:41:10 [---] Received signal 15
2006-05-04 10:41:10 [---] Exit requested by user
2006-05-04 10:41:11 [---] request_reschedule_cpus: exit_tasks

[...]

2006-05-04 10:46:18 [SETI@home] Resuming computation for result 09au01aa.21558.19025.386086.1.87_1 using setiathome version 418
2006-05-04 10:46:18 [SETI@home] Resuming computation for result 16oc02aa.11249.23297.429814.1.115_1 using setiathome version 418
2006-05-04 10:46:18 [---] Suspending work fetch because computer is overcommitted.
2006-05-04 10:46:18 [---] Using earliest-deadline-first scheduling because computer is overcommitted.
2006-05-04 10:48:17 [---] Received signal 15
2006-05-04 10:48:18 [---] Exit requested by user
2006-05-04 10:48:18 [---] request_reschedule_cpus: exit_tasks


[...]

2006-05-04 13:38:08 [SETI@home] Resuming computation for result 09au01aa.21558.19025.386086.1.87_1 using setiathome version 418
2006-05-04 13:38:08 [SETI@home] Resuming computation for result 16oc02aa.11249.23297.429814.1.115_1 using setiathome version 418
2006-05-04 13:38:08 [---] Suspending work fetch because computer is overcommitted.
2006-05-04 13:38:08 [---] Using earliest-deadline-first scheduling because computer is overcommitted.
2006-05-04 13:40:06 [---] Received signal 15
2006-05-04 13:40:07 [---] Exit requested by user
2006-05-04 13:40:08 [---] request_reschedule_cpus: exit_tasks

[...]

2006-05-04 15:23:02 [SETI@home] Resuming computation for result 09au01aa.21558.19025.386086.1.87_1 using setiathome version 418
2006-05-04 15:23:02 [SETI@home] Resuming computation for result 16oc02aa.11249.23297.429814.1.115_1 using setiathome version 418
2006-05-04 15:23:02 [---] Suspending work fetch because computer is overcommitted.
2006-05-04 15:23:02 [---] Using earliest-deadline-first scheduling because computer is overcommitted.
2006-05-04 15:25:01 [---] Received signal 15
2006-05-04 15:25:01 [---] Exit requested by user
2006-05-04 15:25:02 [---] request_reschedule_cpus: exit_tasks

[...]


2006-05-04 15:36:23 [SETI@home] Resuming computation for result 09au01aa.21558.19025.386086.1.87_1 using setiathome version 418
2006-05-04 15:36:23 [SETI@home] Resuming computation for result 16oc02aa.11249.23297.429814.1.115_1 using setiathome version 418
2006-05-04 15:36:23 [---] Suspending work fetch because computer is overcommitted.
2006-05-04 15:36:23 [---] Using earliest-deadline-first scheduling because computer is overcommitted.
2006-05-04 15:38:23 [---] Received signal 15
2006-05-04 15:38:24 [---] Exit requested by user
2006-05-04 15:38:25 [---] request_reschedule_cpus: exit_tasks

I think you should check
this thread
You might find it useful - seems like you have do-work-while-in-use in General Prefences set to "no" and it's doing work only from the time you leave your desk to the time the screensaver is on.

[edit] oops... haven't read above thread to the bottom - but still you might check do-work-while-in-use - maybe that is the case

---

I think you should check
this thread
You might find it useful - seems like you have do-work-while-in-use in General Prefences set to "no" and it's doing work only from the time you leave your desk to the time the screensaver is on.

[edit] oops... haven't read above thread to the bottom - but still you might check do-work-while-in-use - maybe that is the case

I think this may indeed be the answer: My mac only runs BOINC between screensaver coming on and display going to sleep. Which for me is exactly two minutes (I checked my settings: screensaver on after 5 minutes, screen goes blank i.e. off after 7 minutes.)
No wonder I don't get anywhere with my WUs!!

The guy in the above mentioned thread seems to have the same problem. He says:

This is what I found: after 15 minutes and 2 seconds from starting the boinc application I have:

2006-03-07 02:59:41 [---] Received signal 15
[---] Exit requested by user
[---] request_reschedule_cpus: exit_tasks

Then I have the boinc client restarting only the next morning after I moved the mouse. I can't understand why it stopped working, since I didn't bother the screensaver mode.

I've just checked that one of my macs has the screen sleep mode set to 15 minutes, so it could be the origin of the problem, although it's really odd that if the screen goes black boinc manager (the screensaver) stops working.

This may be an OSX system issue then. As I mentioned earlier it does seem kind of pointless to have a screensaver running when the display is off, as they usually don't do any "work" like BOINC.

Is this the end of the screensaver option or do I have to leave my screen on from now on?
Many thanks,
Philipp

Is this the end of the screensaver option or do I have to leave my screen on from now on?

I'd suggest killing it as a screen saver & do as somone suggested earlier in the thread. Set it to run always & see what effect it has (or more likely doesn't have) on system performance over a week or so.

---

Grant
Darwin NT

I think you should check
this thread
You might find it useful - seems like you have do-work-while-in-use in General Prefences set to "no" and it's doing work only from the time you leave your desk to the time the screensaver is on.

[edit] oops... haven't read above thread to the bottom - but still you might check do-work-while-in-use - maybe that is the case

I think this may indeed be the answer: My mac only runs BOINC between screensaver coming on and display going to sleep. Which for me is exactly two minutes (I checked my settings: screensaver on after 5 minutes, screen goes blank i.e. off after 7 minutes.)
No wonder I don't get anywhere with my WUs!!

The guy in the above mentioned thread seems to have the same problem. He says:

This is what I found: after 15 minutes and 2 seconds from starting the boinc application I have:

2006-03-07 02:59:41 [---] Received signal 15
[---] Exit requested by user
[---] request_reschedule_cpus: exit_tasks

Then I have the boinc client restarting only the next morning after I moved the mouse. I can't understand why it stopped working, since I didn't bother the screensaver mode.

I've just checked that one of my macs has the screen sleep mode set to 15 minutes, so it could be the origin of the problem, although it's really odd that if the screen goes black boinc manager (the screensaver) stops working.

This may be an OSX system issue then. As I mentioned earlier it does seem kind of pointless to have a screensaver running when the display is off, as they usually don't do any "work" like BOINC.

Is this the end of the screensaver option or do I have to leave my screen on from now on?
Many thanks,
Philipp

Philipp,

1. As for me - I don't use any screensaver as it takes some part of CPU usage - I just have option to turn the sreen off after 5 minutes :) so maybe you might want to try this solution (really don't know if you can completely turn off the screensaver and leave only switch-off-monitor after x min in this Mac's OS - I use Windoze ;))
2. Check the option in Your Account --> General Preferences --> Do work while computer is in use? and set it to "yes".

Hope you will happily crunch again ;)

[edit] I forgot :-/

3. Check the settings in Your Account --> General Preferences --> Connect to network about every: and set it to low value - IMHO values from 0,1 to 0,5 should work great - test if you upload new WU after finishing old WU

---

just a thought....
if BOINC is set to "Do work while computer is in use? yes", it might give the user a feeling of a slight lag when it is releasing the cpu to userprocesses.

the computer is listed as having 2 cpu's.

why not set BOINC to "Do work while computer is in use? yes" and "On multiprocessors, use at most 1 processors" so the possible feeling of lag is removed, but BOINC will still be getting the full benefit of 1 cpu for most of the day.

hello philou

back in the beginning (1999), the first Performance Tweak for
SETI Classic was to turn OFF the screensaver...!!!

i'm running a P3/800 and doing Enhanced Workunits in about
19 hours...Windoze, of course...

what speed is your PowerMac ???

frank

---

Now from all the info and advice I have received in this thread I have gained two things:

1. Running BOINC at all times in the background does not noticeably affect performance of anything I do.

2. When running BOINC as a screensaver on a Mac, the display must not be allowed to go to sleep via the "Energy saver" System Preference Pane, as the display going to sleep terminates the Boinc app running as a screensaver. To achieve more or less the same effect of the display sleeping, one can set the screen to "go to blank" after a certain amount of time via the (BOINC) Options in the Screensaver System Pref Pane.
(I have tested this now with the BOINC log and this is indeed what happens)


Now the choice of whether to have it run at all times or only as a screensaver, will have to remain a personal one, and it won't always be logic alone which determines the outcome. ;-)

I myself can however happily crunch away as I have for the past years and won't have to be late all the time anymore.
Many thanks!
Philou

Philou:
Here's some specifics for you:

Go to System Preferences. Click on Desktop & Screen Saver. Click on the Screen Saver tab.
Down near the bottom, slide the little toggle all the way to the right to "never". This turns off the built-in screen saver.

Click Show All at the top of the window. Click Energy Saver. On the slider for "Put the computer to sleep when it is inactive for:" slicde it to "never". On the next slider "Put the display to sleep when the computer is inactive for:", slide it to 3 minutes, or five minutes, or whatever you choose. The top slider tells the computer to stay awake and keep working; the second slider tells the computer to turn off the screen even though it's still working (touching a key, or moving the mouse turns the screen back on).

Your computer will now stay on and crunch SETI all the time, except it will stay out of your way while you are working - If you want to see what's going on, go to your Applications/Utilities folder, and double-click on Activity Monitor. Click once on the CPU button down at the bottom to select it, and the little window at the bottom will show you what your CPU is doing. Now click on the label "% CPU" at the top of the columns of names and numbers and it will put all of them in numerical order. You can see exactly how much of the CPUs are taken up at any time by which apps. Now go ahead and start up your web browser, your MS Word, MS Excel, your email, and your iCal, and see how the numbers change. For the graphic at the bottom, Red is OS activity, Green is you working your applications such as typing, browsing the web, moving the mouse, downloading email, etc. Blue is what SETI is using. Black is idle time when nothing is happening. If you now click the red button to close the Activity Monitor window, the AM icon will stay in the Dock and you can see at any given time what your CPUs are doing. The AM does take 2 to 5 % of your CPU cycles, so you won't want to run it all the time, but it will show you how SETI backs off when some other app needs the CPU.

C

---

Join Team MacNN

I have found a logfile (stdoutdae.old) in the directory where the BOINC data is kept, and it looks as though BOINC typically runs for pretty exactly two minutes and the quits. I doubt that I have such a good sense of timing that I exit the BOINC screensaver exactly two minutes after it starts, there must be something else at odds? Any ideas?
Many thanks,
Philipp

(BTW I am aware BOINC is not a screensaver, and I also now it's not saving the screen from anything either...)

Philipp,

The reason I'm trying to push you away from the term "screensaver" is because of how screensavers work.

A screensaver runs only when the machine has been idle for a specific amount of time, and it appears that your machine (OSX?) is killing the screensaver when it blanks the screen.

I suspect you can run this instead as a daemon (I'm a windows user, so I'd say "system service") and then it runs regardless of what the screen is doing.

BOINC as a service gets along and plays well with others: it runs just above the "idle" task, so if anything else wants to run the OS gives the clocks to the other task.

... and my comments are nothing about saving the screen, just about the mechanism used to make BOINC (and the science app.) run.

Make sense?

-- Ned

---

I read this thread and I don't think anyone mentioned that if he has it set to 'run always' and also has it set as a screensaver AND has his monitor set to automatically shut down BOINC should still run all the time whether screensaver is on or monitor is blank. He uses as MAC though so am I wrong??

In case I wasn't clear, it is my contention that if he has it set to run all the time that preogative overrides the problem he's been having with boinc stopping when his monitor goes blank. Am I right here? (I use pc, not mac)

---

Founder of BOINC team Objectivists. Oh the humanity! Rational people crunching data!
I did NOT authorize this belly writing!