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

Watch your OGR buffers

S

SyZ

Junior Member
DNet is letting OGR run dry tonite, and most of their proxies are out of OGR stubs right now. Keep an eye on your clients to make sure you have enough stubs and that you don't fall back to RC5.

That also means there are probably very few OGR24 stubs left, and TA's lead is strong! w()()p!
 
Thanks for the warning. I didn't see anything on their website concerning this. Who's your inside source??? 😉

Well, I set all my machines to do OGR first, then if OGR buffers go dry, switch to RC5. Least I'll stay busy no matter what.

Jay
 
I am buffed up and ready for a drought.

Anybody selling OGR buffers on E-Bay yet?
 
Mika's is out. All that is left is the ones on the baby bovines, which won't last long. I'll be dry in a day probably.

Looking at the rates, looks like Mandrill would be a good person to hit up on, his OGR rate is slower than most of the other Baby Bovines.

Jay
 
These are the only OGR keyservers that have some left. These keyservers are not in the standard round robin of Dnet port 2064 servers, but do run on port 2064 as well as others.

Users can at least download fresh work here, and flush to Mika or the team baby bovines if they wish.

proxy1.red.wa.us.proxy.distributed.net
proxy3.red.wa.us.proxy.distributed.net
proxy3.mtnview.ca.us.proxy.distributed.net

viz
 
Dagnabbit!
Please make sure some of the proxy80 baby bovines get some, or my OGR work herd will run dry. 🙁

And I'm going out of town Sunday. At least they default back to RC5 if they run out..🙂
 
Hmmm... I still see nothing on the d.net site. SyZ, I take it you have inside info (or are an inside person)?

People, any suggestion on how much I should buffer? I've upped myself to 30 stubs for my 880 MHz machine. I figure that should last about 10 days give or take. On my other 6 machines I can't change the config until Monday, but they're only buffering 3 at a time at the moment.

When do you expect Mika's to run dry?

P.S. Should I set the machines to OGR,RC5,DES=0,CSC=0? Right now I have RC5=0, because before I'd get unwanted RC5 blocks being done.
 
Eug,

To give you a guideline at least, For each herd of 5 PIII800s that I have, I usually buffer 200 WU and that will feed them for about 6 days. So for your 6 machines, you could maybe buffer 80-100 and be able to weather almost any stats outage, stub shortage, etc..

-Mike
 
For those of you who might run out of OGR blocks, I will be setting up a private pProxy that only TA members will have access to. One theory is some of the other teams are draining Mika of OGR blocks. I still send the blocks back through Mika, so there is no worry about not getting credit.

Jay
 
Eug, you need to set your project priority to OGR,RC5,DES=0,CSC=0, and your Advanced Buffer Level Checking to 4. This will keep the client working on OGR as long as the keyservers don't run dry, but have it start RC5 if/when they do.
 
I noticed because looking at dnet's ogr proxy status page, the keymaster had 0 stubs available, and several proxies had 0 as well. After a couple hours it was still the same they must be letting it run dry .. and right now only 3 dnet proxies that aren't in heavy usage have ogr stubs. A plan had said they were going to do this a couple weeks ago but it never happened ... guess they finally decided to do it.

- SyZ
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top