To Jator or anyone that uses Jator's pProxy

[DragonFire]

Heres the deal, every block that I get from Jator's pProxy is 3^28 or smaller. A lot of people are telling me it might be all that the server has however, I changed my client to use teamanandtech.dhs.org and I'v been getting all 8^28. Is this a problem with Jator's pProxy or what? Ideas?

 

[Wolfie]

I think it's just the way his pProxy is set up. I get all kinds of sizes depending on what server I get conected too threw the round robin.....

Wolf

 

[dvch]

I think that it is a question of when you get your blocks in relationship to other people. Which reminds me that we should always tell "newbies" to set their block size to 33 and their fetch number divisble by 32;in hopes of causing less fragmentation and being easier on the proxies.

 

[Viztech]

Yup, don't feel alone Dragon Fire. I recently downloaded 110,000 work units, mostly from a Dnet keyserver. Pproxies and keyservers work in 64 work unit packets as a base size, and the pproxies break these packets down to useable sizes for the clients. There is no assurance that we can get that size packetes even from Dnet.
Even though every machine that connects with my proxy is set to request 32 work unit (2^33) packet sizes, I was completely out of that size by the time the in buffer got down to 80,000 work units.
Randoms are probably the root cause of a lot of the small packets that Dnet issues, and client requests for smaller work units will cause further fragmentation in the proxies themselves.
It's one of those things that we all have to deal with.

viz

 

[Jator]

DragonFire,

There is no way to control the block size that a pproxy requests or gives out. Believe me, I wish there were. I too have had a problem getting small blocks as well. I even did a test and went through all the round robin proxies and had similar results. I did seem to get a larger perscentage of large blocks when I went directly to Dnet, but I have to flush through Mika. (This test was done with a Client, not pproxy.)

There are other pproxies out there tht have stats as well. Brad's seems to be up the most, so I would reccomend switching to that one. Trust me, I take no offense to your frustration as I feel it myself.

Jay

 

[Mandrill]

The same goes for my pproxy as well. I have all of my clients set for the 33 blocks but I get all sizes as well.

 

[Jator]

I have switched all my clients here locally to fetch packets divisible by 32. Hopefull this will help reduce some of the fragmentation, but people who use my pproxy can help as well by doing the same thing. My reccomendation is either select 64 or 96 if you have full-time Internet Access, or calculate 3 days worth if you are on dial-up.

Jay