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

Buffering more than 200K in pproxy?

R

Russ

Lifer
It appears that, even in expertmode, the pproxy has an upper limit of 200k blocks. Is there a way around this?

Russ, NCNE
 
Boasting or complaining LOL!!! 🙂

Sorry couldn't resist 🙂

P.S. Sorry, I don't know the answer. I have a hunch something else may be wrong. I know of pproxies that have held much more than 200K
 
Hmm, you could daidy chain 2 pproxies, each holding 200,000 blocks. That way if one runs out, the other would feed the empty pproxy.

Why someone whould need more than 200,000 is beyond me. Oh, wait. It's the cube, right?? 😉
 
Russ: Are you referring to the pproxy holding 200K that is yet to be processed, or holding above 200K that has been processed?
 
As I'm sure you have noticed thecool1.dhs.org currently has an in-buffer of 119K. Perhaps 200K is the limit.

pproxies

Edit: Yes, Mika's is only 50K. My mistake.
 
HMM...could be because he's using a different version of the software. If I set it to anything above 200K, it gives an invalid buffer size message, and sets the minkeys to 200K and the maxkeys to 0 when I restart the pproxy.

Russ, NCNE
 
One possible solution depending on how many of your machines have internet access is to install pproxy on multiple machines and divide the clients among the available pproxies.

This approach could be used even if only one machine has internet access. The additional pproxies could hopefully be configured so that they provide blocks but do not attempt to fetch blocks from a keyserver.

A distributed pproxy if you will.
 
HeHe, I guess I should have checked the readme first before asking a dumb question. The upper limit is, indeed, 200k. I guess I can just setup a second pproxy on my other mandrake box if I actually needed to buffer more. Then map the first in to the second once the in buff is empty.

Russ, NCNE
 
Okay, second pproxy setup and loading the buffer. I now have a nice warm fuzzy feeling having a backup pproxy.😀

Russ, NCNE
 
I had three running the other day.
One for the Rack, one here at home, and my main one I use for my Stats Generator Page.

I'm now down to just two, as I've put the Rack online with the rest of the network at the office.
The old Rack pproxy I had set to only buffer 256 WU, enough to feed the nodes, and then update to the main after 64 WU's done..

I'm happy buffering a 10th of what you want/have. :Q
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top