dnetc .ini autoflush?

[syf3r]

what's the .ini string that causes the client to flush each completed workunit as it is completed, instead of holding the whole thing until the buffer is depleted and, conversely, what is the string that causes it to hold the whole thing until it's done...? i have several machines which i would like to have flush completed units as they are finished, and i have a few that i would like to have hold everything until they finish their complete buffers... thanks...

 

[ViRGE]

Set additional buffer level checking to "2" for the machines that need to flush; and the connection type to "normal" for the machines that need to hold.

 

[RaySun2Be]

ViRGE is correct, and here is the .INI parm:

[buffers]
frequent-threshold-checks=2


Ray

 

[syf3r]

is there a way to comment lines out...?

 

[syf3r]

also, what is the last line in this section?

[rc5]
preferred-blocksize=33
fetch-workunit-threshold=6000
randomprefix=227

some of my clients have a 225, some a 228, some a 227...

 

[dennilfloss]

Interesting, my dialup Borg disk additional buffer level checking is set to '0' and it updates as soon as a packet is completed. What advantage would there be in setting it to '2'?

 

[sciencewhiz]

Denill,

The borg dialup disk uses the dialup detection option 2, which supersedes the additional buffer level checking.

The dialup detection option automatically updates when the computer is connected to the internet and holds when the computer is offline.

 

[dennilfloss]

Cool.

 

[RaySun2Be]

syf3r,
Just put a ; (semicolon) in front of any line you want ingored, the client treats it like a comment.

And I believe the random prefix is something the client uses when cracking random blocks (when it can't get blocks from a server, and runs out of blocks in the buff-in file, it will crack "randoms&quot

I believe it is best to leave it alone and let the client set the prefix.

 

[syf3r]

yeah, i was just curious (re the random packets=225 thing) because i want to install this thing on a few dozen machines, and i planned to just copy the directory and an already configured .ini file along with it so it's ready to go as soon as it's activated. hoping to be able to do 12000+ blocks per day.

 

[RaySun2Be]

syf3r,
Go ahead and make the standard setup and copy, the random prefix won't affect a thing.

12K a day will be an excellent herd!

Just make sure you have permission.

 

[ViRGE]

Actually, you don't need to worry about the random prefix if you use the 464 client; as the random prefix is no longer written in the INI.

 

[syf3r]

okay, so here's what i have:

[parameters]
id=syf3r@hotmail.com

[triggers]
restart-on-config-file-change=yes

[buffers]
frequent-threshold-checks=2

[rc5]
preferred-blocksize=33
fetch-workunit-threshold=6000
randomprefix=225

[misc]
project-priority=RC5,OGR=0,DES=0,CSC=0

[networking]
;dialup-watcher=active
autofindkeyserver=no
keyserver=proxy.teamanandtech.com


now the client seems to be sending each WU as it finishes it. i recall before i made some changes that it was sending them out after it had completed 32 at a time... or was i just imagining this? is there a way to have it wait until it has completed, say, 32 work units, or are the only options really to have it flush after every work unit is completed or flush after the entire buffer is depleted..?

 

[jinsonxu]

try setting

fetch-workunit-threshold=6016

 

[ViRGE]

The best you can do is set how often is does a buffer check. Right now, it's set to check on a buffer change, but adjusting option 11 will allow you to set the interval. By doing that, you could try to time it, so that it flushes around when 32 should be done.

 

[syf3r]

virge: hmm... it's strange though, i was watching my stats this morning as i was eating breakfast and they were going up in multiples of 32.

jinsonxu: i'm guessing because it's a multiple of 32? but the default installation sets a threshold of 2000, doesn't it, which is not a multiple of 32... again, maybe i'm wrong, i've made so many adjustments to this ini i forget what the default is now.

 

[Engineer]

The reason your stats of the client goes up by 32 WU's is because of:

[rc5]
preferred-blocksize=33


Which loads packets with 32 WU's per packet. After each packet is complete, 32 WU's will be placed in your buff-out.rc5 file waiting to be sent.

Welcome to TeAm Anandtech....12K per day will be a beautiful herd!