So, I wanted to know if the other host has comparable values and if both are in the same venue.
Perhaps that client versions also matter. 1945350 is using 6.4.7, 1719080 is using 5.10.13
Quite! I'm dragging my feet on upgrade to newer client version until this issue is resolved.
I noticed a similar hesitancy to fill the buffer on a Q6600 that I have upgraded to 6.4.7. Because of machine stability problems, I've also run it often with local parameters that keep the buffer much lower. Since I couldn't tell you for sure when it was running from my default parameters, I decided not to ask questions about the Q6600.
I really appreciate the effort you folks put into helping me psych this out!
Any contraindications re updating the client to 6.6.36?
If you do, make sure you reset your debts first. BOINC 6.6 uses a whole new debt devising method, unlike any version before that.
To quickly zero debts use Notepad to make a cc_config.xml file in your BOINC Data directory. In it put the following lines:
1
Exit BOINC, save that file in your BOINC Data directory, make sure it has an .xml extension, not a .txt extension. Restart BOINC. Exit it again and edit the cc_config.xml so 1 becomes 0
Save file and restart BOINC. Your debts are now zeroed out.
Excellent! Thank you! That will affect a few machines.
If I don't hear any reasons to not upgrade at this time, I'll go ahead and do so in the next few days. Then will watch and wait for things to get better. Either way, I'll try to remember to come back here and report results.
Any contraindications re updating the client to 6.6.36?
If I don't hear any reasons to not upgrade at this time, I'll go ahead and do so in the next few days. Then will watch and wait for things to get better. Either way, I'll try to remember to come back here and report results.
Well, the update will be delayed a few days until I'm sufficiently recovered from this round of cataract surgery. First eye was easy (10 days ago) ... this one will need some extra time before I can see well enough to do that detail work. Can't evan get my reading glasses on at the moment because of the humongous eye patch the surgeon tpaed on me! Plus side is that surgeon was very proud of this work when done. He is good, anyway and if he is extra proud, that is a good sign!
Thankfully I learned touch typing back when Lassie was a pup, so I can do "safe" things like post to a forum. Holding up a big magnifying glass does help, though, but then I must key one-handed. Reminds me of my Great Aunt Millie! :)
Any contraindications re updating the client to 6.6.36?
If I don't hear any reasons to not upgrade at this time, I'll go ahead and do so in the next few days. Then will watch and wait for things to get better. Either way, I'll try to remember to come back here and report results.
Well, the update will be delayed a few days until I'm sufficiently recovered from this round of cataract surgery.
Update to 6.6.36 mitigated most of the buffer issue. According to BoincView, the buffer promptly filled from 1/4 to about 3/4 capacity as compared to other machines on my LAN running the same parameters. Now it has increased to about 7/8 capacity, so it perhaps ran into a brief WU supply problem, and then into the "per diem" limit!
So, I consider the problem SOLVED! Thanks to all who gave input!
This machine is dedicated to E@h so there was no issue of resetting debt.
Quote:
... Holding up a big magnifying glass does help, though, but then I must key one-handed. Reminds me of my Great Aunt Millie! :)
For those who missed it, the story of Great Aunt Millie is stored at http://stanpope.net/millie.html I kept the thread because it contains some touching comments by some original SETI@home project participants, and because I'm the wag who made up most of the story.
RE: RE: So, I wanted to
)
Quite! I'm dragging my feet on upgrade to newer client version until this issue is resolved.
I noticed a similar hesitancy to fill the buffer on a Q6600 that I have upgraded to 6.4.7. Because of machine stability problems, I've also run it often with local parameters that keep the buffer much lower. Since I couldn't tell you for sure when it was running from my default parameters, I decided not to ask questions about the Q6600.
I really appreciate the effort you folks put into helping me psych this out!
Stan
RE: You can look those
)
I knew of the logs but was too lazy to search for the link :-)
I just wanted to make sure that they both have the same queue size defined. One never knows... ;-)
I would say, that's it. I always knew why I didn't upgrade from 5.10.45 :-)
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
RE: RE: Perhaps that
)
Any contraindications re updating the client to 6.6.36?
Stan
RE: Any contraindications
)
Not by me; as I said, I've never run any version 6 BOINC.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
[quoteAny contraindications
)
[quoteAny contraindications re updating the client to 6.6.36?
RE: RE: Any
)
Excellent! Thank you! That will affect a few machines.
If I don't hear any reasons to not upgrade at this time, I'll go ahead and do so in the next few days. Then will watch and wait for things to get better. Either way, I'll try to remember to come back here and report results.
Stan
RE: RE: Any
)
Well, the update will be delayed a few days until I'm sufficiently recovered from this round of cataract surgery. First eye was easy (10 days ago) ... this one will need some extra time before I can see well enough to do that detail work. Can't evan get my reading glasses on at the moment because of the humongous eye patch the surgeon tpaed on me! Plus side is that surgeon was very proud of this work when done. He is good, anyway and if he is extra proud, that is a good sign!
Thankfully I learned touch typing back when Lassie was a pup, so I can do "safe" things like post to a forum. Holding up a big magnifying glass does help, though, but then I must key one-handed. Reminds me of my Great Aunt Millie! :)
Stan
RE: RE: RE: Any
)
Update to 6.6.36 mitigated most of the buffer issue. According to BoincView, the buffer promptly filled from 1/4 to about 3/4 capacity as compared to other machines on my LAN running the same parameters. Now it has increased to about 7/8 capacity, so it perhaps ran into a brief WU supply problem, and then into the "per diem" limit!
So, I consider the problem SOLVED! Thanks to all who gave input!
This machine is dedicated to E@h so there was no issue of resetting debt.
For those who missed it, the story of Great Aunt Millie is stored at http://stanpope.net/millie.html I kept the thread because it contains some touching comments by some original SETI@home project participants, and because I'm the wag who made up most of the story.
Stan