Message boards :
Number crunching :
% of time client is on - error?
Message board moderation
Author | Message |
---|---|
derekm Send message Joined: 25 May 99 Posts: 9 Credit: 252,163 RAC: 0 |
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 |
Walt Gribben Send message Joined: 16 May 99 Posts: 353 Credit: 304,016 RAC: 0 |
> 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. |
Astro Send message Joined: 16 Apr 02 Posts: 8026 Credit: 600,015 RAC: 0 |
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 |
derekm Send message Joined: 25 May 99 Posts: 9 Credit: 252,163 RAC: 0 |
@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 |
John McLeod VII Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0 |
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 |
Walt Gribben Send message Joined: 16 May 99 Posts: 353 Credit: 304,016 RAC: 0 |
> 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. |
derekm Send message Joined: 25 May 99 Posts: 9 Credit: 252,163 RAC: 0 |
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 |
©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.