The basic idea is, if the server need to send 1000 packets one by one serialized, why not send it parallelized.

-electronixtar (December 20, 2009, 06:12 PM)

Because it doesn't really matter if you have one data stream or fifty. The (ISP Controlled) connection speed (data) pipe is only as big as it is, and trying to force more through it will only cause a flood of retransmits (think turbulence) that will slow down the overall transfer speed.

-Stoic Joker (December 20, 2009, 10:35 PM)

I didn't mean to break the ISP pipe, but some connections are really slow, like 10KB/s compared to my total bandwidth (2M). It's better to open more channels for communication.

Third party download tools (like FreeDownloadManager) are invented for the exactly same reason. What I need is not downloading the whole file by splitting Content-Range, but to transfer packets x3 with three threads.

Just want to know if anything like this exists.

Hi DC,

I have a remote server as a reverse proxy/http proxy, it's kinda slow, I hope there's some kind of software to speed it up a little by doing parallel data transfer.

Does any software like this exist?

My ideal version:

1. The server prefetches 3KB of data
2. The server send to client 3KB of data, but open multithreaded transfer, with 1KB of data per thread
3. The client receives 1KBx3, and combine them to the original 3KB data

The latency is not important as long as the transfer rate is good.

With your ISP screwing around with the DNS queries wouldn't it be better to run your own DNS server?

eg. Treewalk

-4wd (November 24, 2009, 04:42 PM)

It's slow and costs too much memory if you run long enough. Not worth it.

If they're tampering with the actual traffic on port 53, as opposed to just records from their own DNS servers (the impression I got), then you could probably prove it by using DNSSEC (will only work for certain TLDs though, .org is probably easiest).

Ehtyar.

-Ehtyar (November 24, 2009, 06:50 PM)

DNSSec is cool, but not all of TLD have it.