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

MY missing blocks. :(

C

Choralone

Senior member
See this thread for Russ' take on the 12th.

Ok, I finally managed to check my Pproxy log for the 12th and here's what I've found.

There were 7616 total blocks submitted through my Pproxy for the 12th. According to d.net 1097 of them count and not many were added on to my totals for the 13th either. I had 875 blocks according to d.net of which I show 707 went through my Pproxy for the 13th. All the machines that crack for me go through my Pproxy. So either a very large chunk of those missing blocks shows up soon (along with the 3000+ from the 14th) or I'm going to be VERY upset. :| I can understand that a decent chunk of the blocks submitted were in fact randoms, but not nearly THAT many...

What's the point of going to all this trouble if I'm only getting credit for ~15% of the blocks I've submitted on one of my best days ever... <shakes head>

 
Does anyone know how the client pulls the WU from the in-buffer? I'm assuming it's LIFO, but perhaps it just pulls them at random, or even worse, FIFO. If you keep a big buffer, I suppose it's possible/likely that some of the blocks don't get cracked for a while, they are reissued and you end up working a duplicate.
 
I've been wondering that myself with the Pproxy. I don't keep a very large amount of WU onhand, less than 5000. That's enough to keep my machines fed for about 5 days. Although I do have a couple machines that only check in a couple times a month. But I thought that d.net usually waits 30+ days before re-issuing RC5 keys that haven't returned. Can anyone verify this?

I set my limit at 5000 mainly because those machines that only check in a couple times a month can crunch through 3-5K in between the time they've got net access. Although if this continues to be a problem I'll find a way to get those machines to check in once a week.

Does anyone else have a substantial amount of work missing from the 12th?
 
Jim-

The clients will crack the lowest numbered block in the in buffer first.

Proxies on the other hand will tend to bury the fragments in their in buffers. In other words, they will break down a perfectly good 64 WU packet to feed even a 1 WU packet to a client. That's why I will drain my Pproxy once a week or so. Those fragments that it drains out get kinda old.

I keep my clients asking for 32 WU packets, but Mika and Jator send me those tiny ones.

viz
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top