Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

International File transfer

Status
Not open for further replies.

mmaleh

IS-IT--Management
Jun 18, 2003
67
US
Hello everyone,
I have an office in NYC, one in San Fran and one in China. When I transfer files between NYC and SF I get great speeds. But any time we transfer between china and either US offices the speeds are very slow (like 4k/sec) We tested the speeds in china transfering from one china site to the next and they were getting great speeds but when they did from china to the us the day the speeds were very slow. what could be causing this? is this a routing problem?
-m
 
I doubt its a routing problem but you need to do some traceroutes and see where the delay is . 4K isn't even 56K dialup transfer speeds . Look at your net maps and trace and do pings to each hop along the way and somewhere it will show up as a site or hop that is a lot slower . Also you could have your international carrier check the overseas line you are using . Any errors on the interfaces that feed the china links ?
 
no errors on the interfaces that feed the china links.
I will do a tracert and send the results.
One of the carriers over there that I spoke with tried to blame it on the "pipe coming out of china" I had a hard time believing this.
-marc
 
C:\Documents and Settings\m.maleh>tracert gz.screampoint.com

Tracing route to gz.screampoint.com [218.20.56.169]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.50.0.1
2 2 ms 2 ms 1 ms custnets-66-43-100-225.rinc.net [66.43.100.225]
3 5 ms 5 ms 5 ms custnets-66-43-83-89.rinc.net [66.43.83.89]
4 23 ms 15 ms 18 ms 66.43.68.33
5 14 ms 16 ms 18 ms 66.43.64.33
6 17 ms 7 ms 6 ms hagg-01-t3-1-0-2-0.nycl.twtelecom.net [168.215.100.161]
7 17 ms 17 ms 17 ms core-01-ge-0-1-1-510.nycl.twtelecom.net [66.192.253.64]
8 95 ms 109 ms * core-01-so-4-1-0-0.okld.twtelecom.net [66.192.250.96]
9 133 ms 110 ms 117 ms peer-01-so-0-0-0-0.palo.twtelecom.net [66.192.250.44]
10 105 ms 105 ms 98 ms 66.192.252.30
11 102 ms 97 ms 97 ms 202.97.49.194
12 265 ms 262 ms 272 ms 202.97.51.229
13 359 ms 362 ms 373 ms 202.97.33.157
14 362 ms 356 ms * 202.97.40.110
15 369 ms 371 ms 356 ms 61.140.17.9
16 402 ms 386 ms 399 ms 61.144.0.154
17 399 ms 399 ms 399 ms 61.144.9.26
18 * 373 ms 363 ms 61.144.9.107
19 * 376 ms 382 ms 218.20.56.169

Trace complete.


This is a trace I did from my office in NYC to the office in china.
 
Steps 1 to 7 are in or near NYC NY, delay is under 20 ms, mostly electronics.

Steps 8 to 11 are in California, delay is around 100 ms, mostly speed of light.

Step 12 may be in China, if so, it may not be near your offices, as it is only 270 ms to here, but

Step 13 to 19 are in China, 360 to 400 ms delay to get to these sites.

So for protocols requiring an ACK for every data packet, china will be 20 times slower than New York. (and same effect in China) I would look at a 'sliding window' file transfer protocol with very large windows.



I tried to remain child-like, all I acheived was childish.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top