• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

crunching randoms?

toph99

Diamond Member
what does it mean if you are crunchin randoms in rc5 as opposed to what you are usually doing? how can i tell if my computers are crunching randoms or not?
 
If it's crunching randoms, it will say so in the window when it loads a random block. Crunching randoms means that it is checking blocks that it picked itself, instead of blocks that a Dnet keyserver or PProxy gave to it as "known unchecked" blocks. Typically, some of the randoms end up being ones that have already been checked, so they are duplicates and don't count. Loss is typically in the 30-40% area, I think.
 
Yep... that's what does it.
If that happens often, just bump up the 'ol in-buffer and it'll happily munch away.

In your [RC5] section add:

fetch-workunit-threshold=xxxx

where x= the number of blocks you want it to hold. Just remember to flush! 🙂
 
I set my client up to fetch/flush every half-hour by enabling "Additional buffer-level checking" to "2" and specifying "0:30" in the "Buffer level check interval" right below it. Both of those are in 2) Buffer and buffer update options in the client configuration menu, which is accessed by right-clicking in the client's window and choosing "Configure."

This has it check periodically for the need to fetch/flush, without harassing the pProxy or keyserver too frequently.
 
Back
Top