Multi-threaded copy / download tools?

Started by Dieselboy, October 05, 2015, 02:38:47 AM

Previous topic - Next topic

deanwebb

If I had a kb for every time it was mixed up with KB, I'd have a KB.
Take a baseball bat and trash all the routers, shout out "IT'S A NETWORK PROBLEM NOW, SUCKERS!" and then peel out of the parking lot in your Ferrari.
"The world could perish if people only worked on things that were easy to handle." -- Vladimir Savchenko
Вопросы есть? Вопросов нет! | BCEB: Belkin Certified Expert Baffler | "Plan B is Plan A with an element of panic." -- John Clarke
Accounting is architecture, remember that!
Air gaps are high-latency Internet connections.

packetherder

Quote from: Dieselboy on October 06, 2015, 08:44:28 PM
Wintermute I used the same website:
Quote
Bandwidth-delay Product and buffer size

BDP (100 Mbit/sec, 340.0 ms) = 4.25 MByte
required tcp buffer to reach 100 Mbps with RTT of 340.0 ms >= 4150.4 KByte
maximum throughput with a TCP window of 64 KByte and RTT of 340.0 ms <= 1.54 Mbit/sec.

so, 1540000 bit /8 = 192.5kbyte/s total bit rate.
Add on VPN headers, the odd packet loss (as some packets do get lost), as well as TCP / FTP headers I expect this is why I'm getting around 180k, roughly.

Although I have seen single connections sometimes getting quite high throughput yesterday, 400k.

What's the deciding factors to go above 64k window size? I'm going to install wireshark and see what is going on.
:rock:

afaik, XP doesn't initiate window scaling by default, and from what I've read, neither does Win7 in some configurations (e.g. "Public" networks). There are registry hacks you can do for both to enable though. I've run into this exact issue with a long-fat connection where $stupidapp didn't do connection parallelization or window scaling. Easiest way to confirm is to see what's happening in wireshark but the math certainly seems to suggest that's the case.

NetworkGroover

Quote from: Dieselboy on October 07, 2015, 01:52:42 AM
I always get confused with k K b B. I've looked it up so many times. Still confuses me about which way round it goes.  :(

The "k" is always lower case, AFAIK.

b is lower case, and "smaller" than B, as bits are smaller than Bytes.

m is lower case, and "smaller" than M, as milli is smaller than Mega - so for us in the networking world... I don't think you'll see a lower case m too much.
Engineer by day, DJ by night, family first always

SimonV

Quote from: AspiringNetworker on October 07, 2015, 11:07:23 AM
m is lower case, and "smaller" than M, as milli is smaller than Mega - so for us in the networking world... I don't think you'll see a lower case m too much.

My ping command shows it all the time  :(

Reggle

Quote from: SimonV on October 07, 2015, 11:37:04 AMMy ping command shows it all the time  :(
Reply from 8.8.8.8: bytes=32 time=7Ms TTL=3