• 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.

Why does DNet show less blocks than Mika's?

S

Sukhoi

Elite Member
I just checked, and Mika's has me at 1554 blocks and DNet has me at 1400. I know I have nothing stuck at Mika's because all the blocks I flushed yesterday have shown up at DNet. So, why am I missing 154 blocks, which is 9% of my total output? If this happens anymore, I'm sticking my DX4-100 and P133 back onto SETI, even if they take a week to do a WU.

I can understand Mika's being lower than DNet's, since I know I've flushed some blocks straight to DNet before, but having the problem the other way around makes no sense.
 
Sukhoi: I've seen the same thing! 🙁 I can only assume that it is due to randoms. But, others disagree. If it is due to Randoms, then it will only get worse as the project progresses. I quit worrying about what is on d.net and use Mika's Stats.
 
Most of the missing blocks are from randoms. But I guess there is a slight case of ppl actualy missing a LOT of blocks.... Personaly.. I am only missing about 4K out of 280K.... So It guess that isn't tooooooo bad.

Wolfie
 
But I don't understand how it's randoms if I've only had these blocks cached on my computer for under a week?
 
It's not how long you've had the blocks cached, it's how long Dnet's been using this particular slice of keyspace. If we're near the end, then randoms will have allready filled in at least a decent chunk.
 
Oh, that kinda makes sense. But 9% randoms is a little high...

Why doesn't DNet open up a separate keyslice farther on, and have the randoms work on it? Then some of it would be cleared out when DNet actually got to it to send blocks out from that keyslice.
 
I think the small keyslice has to do with disk space. In a past thread, LeBlatt and myself were going over the total size of Dnet's block DB, and came to the conclusion that it'll be about 1.4TB if every block is checked. Right now, there's reliable way in heck of even holding 10% of that on a HD, meaning that Dnet has to keep a small fraction open in order to keep the active part of the DB within the limits of the keymaster's disk system. Since letting randoms work too far ahead would make the DB too big, it really isn't an option; hence where we are.🙁
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top