I have been a SETI member since Dec 2000. My BOINC application shows that I have 1,053,483 work credit. I am currently using BOINC 7.0.31 but have noticed that my avg work has been going down and is currently 0.15 units which is considerably lower than it has been for a long time. I have NO tasks in queue.

This issue was present before I updated to Mountain Lion (10.8) but I thought that there were server issues as noted in the previous messages. I no longer think that. I do have moderate computer skills, am familiar with the command line, and have done some perl (web work) programming experience.

I currently do have two other projects running on BOINC. All three have equal resources. The first two do receive work from their project servers.

I have noticed that the BOINC software does not connect to my local computer projects (the screen saver says the client is not running) even though I can see a version of BOINC is running which I can quit. When I click on the same dock icon, it does connect to my local computer and does show the work being done by it but no SETI.

... what are the values for:
% of time BOINC is running 91.1347 %
While BOINC running, % of time host has an Internet connection 99.3118 %
While BOINC running, % of time work is allowed 99.9754 %
Task duration correction factor 1.829205

(the above values are from one of my computers, only you can see yours)

... what are the values for:
% of time BOINC is running 91.1347 %
While BOINC running, % of time host has an Internet connection 99.3118 %
While BOINC running, % of time work is allowed 99.9754 %
Task duration correction factor 1.829205

(the above values are from one of my computers, only you can see yours)

The seti page shows:
% of time BOINC is running 20.7241 %

[Is this calculated time? Or can I control it? Is is a factor of when the computer goes to sleep or ...?]

While BOINC running, % of time work is allowed 99.9725 %

Average CPU efficiency 0.891583 [!!!! Isn't this extremely low?]

Task duration correction factor 1.055866

While the climate page shows:
Average turnaround time 91.31 days
Maximum daily WU quota per CPU 1/day

The quake catcher network preferences page shows:

Suspend work while computer is on battery power?
Matters only for portable computers yes
Suspend work while computer is in use? no
Suspend GPU work while computer is in use?
Enforced by version 6.6.21+ yes
'In use' means mouse/keyboard activity in last 3 minutes
Suspend work if no mouse/keyboard activity in last
Needed to enter low-power mode on some computers --- minutes
Suspend work when non-BOINC CPU usage is above
0 means no restriction
Enforced by version 6.10.30+ --- %
Do work only between the hours of
No restriction if equal ---
Leave tasks in memory while suspended?
Suspended tasks will consume swap space if 'yes' no
Switch between tasks every
Recommended: 60 minutes 60 minutes
On multiprocessors, use at most 7 processors
On multiprocessors, use at most
Enforced by version 6.1+ 100% of the processors
Use at most
Can be used to reduce CPU heat 100% of CPU time
Disk and memory usage
Disk: use at most 200 GB
Disk: leave free at least
Values smaller than 0.001 are ignored 10 GB
Disk: use at most 50% of total
Tasks checkpoint to disk at most every 60 seconds
Swap space: use at most 75% of total
Memory: when computer is in use, use at most 50% of total
Memory: when computer is not in use, use at most 90% of total
Network usage
Computer is connected to the Internet about every
Leave blank or 0 if always connected.
BOINC will try to maintain at least this much work. --- days
Maintain enough work for an additional 0.25 days
Confirm before connecting to Internet?
Matters only if you have a modem, ISDN or VPN connection no
Disconnect when done?
Matters only if you have a modem, ISDN or VPN connection no
Maximum download rate: --- Kbytes/sec
Maximum upload rate: --- Kbytes/sec
Use network only between the hours of ---
Transfer at most
Enforced by version 6.10.46+ --- Mbytes every --- days
Skip image file verification?
Check this ONLY if your Internet provider modifies image files (UMTS does this, for example). Skipping verification reduces the security of BOINC. no

1. Yes, I do have Climate Prediction running. I currently have seven tasks, Boinc Manager reports one as "running," five "Running, High Priority,"and one "Ready to Start,"

'Running, High Priority' is one of the things that can make BOINC not request new tasks.
('High Priority' means 'Run that task first, it is in danger to miss the deadline')
BOINC is in panic mode - it thinks it will not have enough computing time.

Maybe because you changed your habits?
Maybe in the past months you used the computer for 12 hours/day - then BOINC get enough tasks to 'fill' that time (for months ahead (?) since Climate Prediction tasks are long (as I heard, I do not run Climate Prediction))

But now you use the computer (together with the running BOINC) for 5 hours/day (% of time BOINC is running 20.7241 % - this is % of wall clock time, your computer is shutdown/sleeping 80% of the day)

Or maybe BOINC was underestimated the Climate Prediction tasks (e.g. was thinking the task will be computed in 1 month but now realize it will need 5 months)

Average CPU efficiency 0.891583 [!!!! Isn't this extremely low?]

Not important value (not used by BOINC to make decisions), I think the max for this is 1.0 (and I'm not sure how this is calculated, it does not show the speed of the CPU)

Network usage
Computer is connected to the Internet about every --- days
Leave blank or 0 if always connected.
BOINC will try to maintain at least this much work.

Maintain enough tasks to keep busy for at least XX days
(max 10 days).
... and up to an additional YY days

Change ---/XX to e.g. 3 days

Do the change at one project (e.g. SETI) - it will propagate to others automatically when you [Update] from BOINC Manager all of projects
(first the one where you did the change of 'Computing preferences')

1. Yes, I do have Climate Prediction running. I currently have seven tasks, Boinc Manager reports one as "running," five "Running, High Priority,"and one "Ready to Start,"

'Running, High Priority' is one of the things that can make BOINC not request new tasks.
('High Priority' means 'Run that task first, it is in danger to miss the deadline')
BOINC is in panic mode - it thinks it will not have enough computing time.

Maybe because you changed your habits?

Maybe in the past months you used the computer for 12 hours/day - then BOINC get enough tasks to 'fill' that time (for months ahead (?) since Climate Prediction tasks are long (as I heard, I do not run Climate Prediction))

But now you use the computer (together with the running BOINC) for 5 hours/day (% of time BOINC is running 20.7241 % - this is % of wall clock time, your computer is shutdown/sleeping 80% of the day)

I will check the power manager settings and set to dim monitor and not sleep... Maybe that will help. I will allow the hd to spin down when not needed.

Or maybe BOINC was underestimated the Climate Prediction tasks (e.g. was thinking the task will be computed in 1 month but now realize it will need 5 months)

Now, I am really concerned. I have not set any priority. When I inspect the Tasks in the manager screen, I see this...

The due dates on the projects are what are concerning to me. I also noticed that a lot of my SETI projects timed out due to being late.

I think that the rest of my computer issues will fall in line when I get this straightened out.

As far as typing. I program web stuff and am trying to learn C++ so maybe I should look into voice transcription applications.
____________

and the other two checked but I don't see how allowing the power button to put the computer to sleep nor restarting after a power failure would do anything but help production.

So the power settings are not hurting Boinc as I can see it.

I will check with Climate Prediction and see what is up with the tasks that I do have on board.

As I left this post to get to the CP website via the BIONC Manager app and I noticed that the status appeared to be the same as the screen shot that I had taken so to be sure, I opened up the screen shot and compared them. They were identical and despite the dock indicating that it was running, the seconds indicator showing progress was not showing any incremental changes. On a hunch, I quit BOINC Manager and restarted it. Now it is progressing.

Not you, BOINC do this automatically if it thinks the task is in danger to miss the deadline.
The 'High Priority' means only reordering of the tasks (which of them will be computed now), no Process Priority is changed.

The due dates on the projects are what are concerning to me.

Yes, they (those 'Running, High Priority') are due in Aug 2012, you probably will not get credit for them.
(did your computer remain OFF for a long time (weeks,months)?)

For now [Suspend] all that are 'Running, High Priority' (they are not in your task list on the site)
except the one at 91% Progress/25h Remaining
(to see if you will get credit for it after reporting it - if No credit given - [Abort] all that are due in Aug 2012)

Suspending high priority tasks only throws BOINC's internal scheduler further off. Since those ClimatePrediction tasks are already past due, you may want to consider aborting them as you likely won't get credit for them.

BOINC Manager is just a GUI for the BOINC Framework. None of the workunit processing is handled by BOINC Manager or the BOINC Core Client. If an application stops progressing, the issue must lie in the science app used to process the work.

I did suspend, will about those tasks, while doing that I noticed that I had about a 50 second hold before the Manager was to communicate with SETI after that lapsed, I received 9 tasks from SETI, five of wihich are currently running.

Thank you for your help. Now to figure out what is halting Boinc on my machine.
____________

I did suspend, will about those tasks, while doing that I noticed that I had about a 50 second hold before the Manager was to communicate with SETI after that lapsed, I received 9 tasks from SETI, five of wihich are currently running.

So BOINC was trying to meet past deadlines for ClimatePrediction, as it is programmed to do, and therefore it didn't want to request any additional work because it was already in (past) deadline trouble.

By forcing BOINC to suspend past due tasks and request new work, BOINC's internal calculation for your system's uptime and efficiency will be off, which in turn will mess up future requests for work as those stats are used to find out how much work to retrieve from a project.

Thank you for your help. Now to figure out what is halting Boinc on my machine.

BOINC attempts to contact a project's servers. If the server is overloaded (like SETI's is almost constantly), or if the user forces communications to a project too frequently, the server will tell the BOINC client "hold on a minute" in hopes that it will be less congested later. If it still isn't, the server will request that BOINC keep increasing the amount of time to wait until the next server contact.

Suspending high priority tasks only throws BOINC's internal scheduler further off. Since those ClimatePrediction tasks are already past due, you may want to consider aborting them as you likely won't get credit for them.

ClimatePrediction is the exception to the rule, as you'll get credit even if you return a task (far) beyond deadline.

Suspending high priority tasks only throws BOINC's internal scheduler further off. Since those ClimatePrediction tasks are already past due, you may want to consider aborting them as you likely won't get credit for them.

ClimatePrediction is the exception to the rule, as you'll get credit even if you return a task (far) beyond deadline.

Gruß,
Gundolf

I wish I had seen this before I had aborted the Tasks, would have resumed one at a time.
____________

Suspending high priority tasks only throws BOINC's internal scheduler further off. Since those ClimatePrediction tasks are already past due, you may want to consider aborting them as you likely won't get credit for them.

ClimatePrediction is the exception to the rule, as you'll get credit even if you return a task (far) beyond deadline.

Gruß,
Gundolf

I wish I had seen this before I had aborted the Tasks, would have resumed one at a time.

Even so, manually suspending tasks would have messed with BOINC's internal scheduler even if the project is willing to reward late tasks.