Ugggh... Bad day

[Marty]

329 blocks were completed yesterday (0.00000048% of the keyspace)
at a sustained rate of 1,022 KKeys/sec! Ranked 20,666 for the day.

This is about 8% of the rate of this participant's best day ever, which was
29-Jun-2000 when 4,118 blocks were completed at a rate of 12,794 KKeys/sec.

This is because the dnet keyserver was down for much of the day. I have to reconfigure two of my computers, they just buffer 200 and 100 blocks each. I have a feeling they were cracking mostly randoms yesterday. I'll have to put the new client on them and make them flush every 2 hours, while buffering 2000+ blocks. Maybe next week.

This will hurt me in the four cow race to 100K.

Marty

 

[Engineer]

Marty,

Next time, set your keyserver to clueless.2y.net and run there...Clueless Pproxy flushes through Mika's, therefore no randoms or stats loss...

I have remote buffering which will allow each computer to fall back to a keyserver (clueless) if the main PC buffer is dry...Always 4000 blocks ready to go

 

[Viztech]

Engineer-

That is an interesting idea, Could you explain that further for us?

viz

 

[Engineer]

Viztech,

I have a central PC (both at home and work) with a shared RC5 directory. This PC flushes directly to Clueless.2y.net..

I have a buffer that is maintained at 4000 blocks on that PC. I have my other PC's "Remote Buffer Directory" set to that directory as well as have Remote Buffering enabled. I also have Keyserver enabled and set to clueless.2y.net on each of those PC's. If clueless is down (or Mika), etc. there is at least 4000 blocks waiting to be shared by my PC's. Not a huge amount, but better than pure randoms. If I can figure out why it will only buffer 4000 blocks, I'd increase it to 10000 or so...Better than nothing. I've increased it, but the internal limits will still not allow over 4000 blocks...

Good Luck!

 

[Viztech]

Engineer-

I use remote buffers as well on 2 LANS. One is strictly on sneakers, while the other uses 2 servers as the shares, these servers connect to Mika via manual dial up. Both of these will be changing drastically in the near future, as I get full time connectivity on one LAN with my own PProxy on the firewall box.

I think that the reason you are limited to 4000 blocks is that you have your preffered packet size set to 2^31 which equals 8 WU packets.
The clients have an internal limit of 500 packets therefore 8x500=4000 WUs. I set the preffered packet size to 2^33 (32 WU) which then has a theoretical maximum of 16,000 WUs. I say theoretical, as packets this large are becoming more difficult to come by. In reality, I can usually only get ~6-7000 WUs buffered when drawing from Mika due to the mixture of large and small packets.
I try to ensure that all work gets returned to Dnet before 3 weeks go by, so they do not get reissued.

OK, as I understand it, each of your clients has full time Internet connectivity, so they normally flush to/from Clueless on their own.
If you have a communication failure to Clueless, your other clients fallback to the shared remote buffers on a client with 'no fallback' enabled on all clients.
If the client with the remote buffer share fails, you are still using Clueless on the other clients.
Do I have the right idea here?

Thanx
viz

 

[Engineer]

As far as your last paragraph, that is correct....

When one goes down, the others keep going...If both go down....Well....

When going to the "Disable Remote Buffers" section of the client, the page help states that the client will retrieve from Remote Buffer if Keyserver is disabled or if client fails to get enough keys or can't connect...(No quote, just paraphrase...)..

P.S. I just set my main PC up at home with the new client and have it update its buffers every 1/2 hour to make sure that I always have a nice fat bail (spelling?) of hay in the barn for the Mooooooooooo's to chew on

Good Luck!