There isn't really anything the proxy in and by itself can do to help you out

-f0dder (December 21, 2009, 03:09 PM)

I am looking for this kind of software. Thus this post.

-electronixtar (December 21, 2009, 03:20 PM)

And I'm saying it can't be done without client+server support :). If you're talking HTTP connections, then something could be done - the proxy could split client requests into multiple server requests with varying content-length... but that wouldn't buy you very much, and if the bottleneck is between client->proxy, then it buys you nothing at all.

Anyway, I'm getting 2MB/s with regular TCP connections on my 20Mbit line, so...

-f0dder (December 21, 2009, 03:09 PM)

I am so jealous

-electronixtar (December 21, 2009, 03:20 PM)

:)

I started with a 512/128 line, and switched to 4096/256 when I figured out it was only $20/month more expensive. Since that, my ISP has been doubling my speed every now and then... too bad I've pretty much hit the limit of what ADSL2+ offers, hope they'll start reducing price soon, or move me to VDSL :P

-f0dder (December 21, 2009, 03:25 PM)

Yes a client+server pair is needed. My remote server can prefetch http resources fast enough, it's just the proxy -> me part is slow if using a normal HTTP proxy.

Why should you worry about my udp transporting speed? I can download BitTorrent fast enough.

-electronixtar (December 21, 2009, 01:05 PM)

I don't really worry about your UDP speed, all I'm saying is that (unless rate-limited some way), UDP goes full throttle and pumps out packets as fast as your link can handle - unlike TCP which does congestion control, and has slow-start.

BitTorrent uses TCP and not UDP, but has massively parallel connections - but you probably already know that.

It's just one personal remote server (reverse proxy) which is transferring data really slow. What should I do? I can't wait all the http resources to be full downloaded then use multithreaded download tools to download them because they are requested on demand. So what's your guy's suggestion?

-electronixtar (December 21, 2009, 01:05 PM)

You really need to explain in more detail what it is you want to do, and which software is involved. As I've already mentioned, you can't just automagically make a proxy parallelize things without client+server support...

-f0dder (December 21, 2009, 02:27 PM)

Oh btw, BitTorrent is way faster in UDP, perhaps you are choosing the wrong client  :P

If it's a custom protocol, how on earth would a generic proxy server be able to automagically split the workload for you? :) - you can't just say "take this data stream and split it into three new ones", that kind of thing requires support both in the client and server side programs.

If your UDP data rate is poor, it's either because one (or both) end(s) are rate-limited somehow, or because the protocol is designed poorly (waiting for ACKs). With TCP you can gain a little by multiple connections even if there's no rate-limiting going on, but UDP always goes full throttle and shouldn't benefit from parallelizing - au contraire.

-f0dder (December 21, 2009, 02:53 AM)

I can download BitTorrent fast enough. It's just one personal remote server (reverse proxy) which is transferring data really slow. What should I do? I can't wait all the http resources to be full downloaded then use multithreaded download tools to download them because they are requested on demand. So what's your guy's suggestion?