Optimum Dnet settings?

[Tripleshot]

I have had to re install the client on all my PC's and after doing so,I'm not convinced I have the right settings to maximize my WU crunching time. I have RC5=1 and all others set to =0. What else do I need to do?

 

[RaySun2Be]

Tripleshot,

Here are some parms I use:

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

[triggers]
restart-on-config-file-change=yes
pause-on-no-mains-power=yes <----------I have a laptop. this helps extend uptime while on battery

[display]
detached=yes <-----------------I run the client as a service so it is hidden
progress-indicator=off

[rc5]
preferred-blocksize=33 <-------recommended
fetch-workunit-threshold=320 <--------this should be set to a multiple of 32
randomprefix=31

 

[Tripleshot]

Thanks Ray. I'm going to adjust now. Do you suggest I remove the =1 after RC5 in the 2/9 setup?

 

[RaySun2Be]

Depends. Which parm label [xxx] is that RC5=1 under?

Oh, I also recommend using a checkpoint file:

[buffers]
buffer-file-basename=buff-in
output-file-basename=buff-out
checkpoint-filename=ckpoint <-----causes a bit more HD access, but saves work every 10% or so, so in case of a crash, you won't lose the work unit, only that amt of work done since the last checkpoint. ie, if you had a WU 93% complete and you get a BSOD, it would start back up at the 90% mark, so you only lose 3% of the work completed, not the entire WU. I think it's worth the extra HD access. 🙂

 

[Tripleshot]

Ray, it's the load work preference setting. The =-1 I think forces default WU size. Section 12 in buffer and update options.

 

[Tripleshot]

I set the fetch level to 350. I hope that didn't screw anything up. Its still crunching.

 

[RaySun2Be]

It doesn't screw anthing up, but may cause the keyserver to break up packets to provide the work units.

And I change the RC5=-1 to RC5=33 in order to get the largest WUs per block possible.

 

[Tripleshot]

Done deal. Thanks again Ray.