% of time client is on - error?

Message boards : Number crunching : % of time client is on - error?
Message board moderation

To post messages, you must log in.

AuthorMessage
derekm

Send message
Joined: 25 May 99
Posts: 9
Credit: 252,163
RAC: 0
United States
Message 64503 - Posted: 14 Jan 2005, 3:38:58 UTC

If I check the "% of time client is on" and other similar stats for one of my computers (Mac OS X MDD G4 Dual 1.0GHz), BOINC says it is 0.0058%. Consequently, this computer will request only 8 seconds of work at a time from S@H and PP@H. With WUs obviously longer than 8 seconds, it usually only downloads one at a time no matter what other prefs I adjust.

This computer is on with BOINC going virtually 24/7 and most definitley not 0.0058% of the time. How can I correct this problem? I could probably detach, reattach, and then not merge the two together. Or could I?

Any ideas? Turn the computer off for a few weeks and assume the problem is that it is actually on 100.0058% of the time and a shutdown will put it back under 100%?

I'm really hoping someone has firsthand knowledge of this problem. f this was answered before, I sure couldn't find the thread. TIA
derekm
Team MacAddict
ID: 64503 · Report as offensive
Walt Gribben
Volunteer tester

Send message
Joined: 16 May 99
Posts: 353
Credit: 304,016
RAC: 0
United States
Message 64506 - Posted: 14 Jan 2005, 3:44:20 UTC - in response to Message 64503.  
Last modified: 14 Jan 2005, 3:44:57 UTC

> If I check the "% of time client is on" and other similar stats for one of my
> computers (Mac OS X MDD G4 Dual 1.0GHz), BOINC says it is 0.0058%.
> Consequently, this computer will request only 8 seconds of work at a time from
> S@H and PP@H. With WUs obviously longer than 8 seconds, it usually only
> downloads one at a time no matter what other prefs I adjust.
>
> This computer is on with BOINC going virtually 24/7 and most definitley not
> 0.0058% of the time. How can I correct this problem? I could probably detach,
> reattach, and then not merge the two together. Or could I?
>
> Any ideas? Turn the computer off for a few weeks and assume the problem is
> that it is actually on 100.0058% of the time and a shutdown will put it back
> under 100%?
>
> I'm really hoping someone has firsthand knowledge of this problem. f this was
> answered before, I sure couldn't find the thread. TIA
>

Stop BOINC and edit the client_state.xml file. Look for the "time_frac" tag and change the .0058 to something more reasonable like .9958. Save the file and start BOINC again. Should be fixed.
ID: 64506 · Report as offensive
Astro
Volunteer tester
Avatar

Send message
Joined: 16 Apr 02
Posts: 8026
Credit: 600,015
RAC: 0
Message 64507 - Posted: 14 Jan 2005, 3:47:42 UTC

What is your "Connect to the network every ____ days" setting? It's found from the main page, click on "your account", then "general preference" then look under Network Usage. This determines how many Work Units you will get. Note: try to keep it under 5 or 6 days.

Then right click on the B in the task bar, or if the boinc window is open; check to see if you've selected "Run Based on Preferences" or"Run Always" selected. I use Run Always.

tony

ID: 64507 · Report as offensive
derekm

Send message
Joined: 25 May 99
Posts: 9
Credit: 252,163
RAC: 0
United States
Message 64515 - Posted: 14 Jan 2005, 3:54:12 UTC - in response to Message 64506.  
Last modified: 14 Jan 2005, 3:59:32 UTC

@Walt

Genius. I never would have guessed it was locally stored and editable. I once changed the client_state.xml file to tell BOINC not to wait 247 days to connect to PP@H. (That's right... I said 247 days. They were down for a while you know ;^) ).

We'll see what happens when it updates the prefs. I have no doubt it will work. Thanks for all the replies! [edit] It's fine now.
derekm
Team MacAddict
ID: 64515 · Report as offensive
John McLeod VII
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 15 Jul 99
Posts: 24806
Credit: 790,712
RAC: 0
United States
Message 64581 - Posted: 14 Jan 2005, 5:00:35 UTC

My guess is that the machine was off for a while after installing BOINC. This would account for the extremely low on frac. It should fix itself after a while of being on 24/7 again.


BOINC WIKI
ID: 64581 · Report as offensive
Walt Gribben
Volunteer tester

Send message
Joined: 16 May 99
Posts: 353
Credit: 304,016
RAC: 0
United States
Message 64691 - Posted: 14 Jan 2005, 7:29:03 UTC - in response to Message 64581.  
Last modified: 14 Jan 2005, 7:31:07 UTC

> My guess is that the machine was off for a while after installing BOINC. This
> would account for the extremely low on frac. It should fix itself after a
> while of being on 24/7 again.
>

I had the same problem with one of my machines. It was down for almost two months, its at a remote site that isn't easily accessable.

The uptime percentage stayed very low, increased only gradually. Wasn't much past 50% even after a month of 24x7 uptime. Did make t hard to get a full weeks worth of WU's.



ID: 64691 · Report as offensive
derekm

Send message
Joined: 25 May 99
Posts: 9
Credit: 252,163
RAC: 0
United States
Message 65761 - Posted: 14 Jan 2005, 15:12:38 UTC

Thanks for the suggestions everyone, but I know for a fact that in the past 7 months this computer has been running BOINC, I've been up for more than 20 minutes. I know it was originally 99.xxx% up for the longest time, and then one day it decided to be 0.0058% up instead. It's a bug of unknown origin. The only other possibility is that I accidentally changed the client_state.xml file in a negative way when I successfully told BOINC to contact PP@H in 100 seconds instead of 21,000,000 seconds.
derekm
Team MacAddict
ID: 65761 · Report as offensive

Message boards : Number crunching : % of time client is on - error?


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.