At the moment we're trying to decide whether to move our datacenter from the west coast to the east coast.
However, I am seeing some disturbing latency numbers from my west coast location to the east coast. Here's a sample result, retrieving a small .png logo file in Google Chrome and using the dev tools to see how long the request takes:
It makes sense that Corvallis, OR is geographically closer to my location in Berkeley, CA so I expect the connection to be a bit faster.. but I'm seeing an increase in latency of +100ms when I perform the same test to the NYC server. That seems .. excessive to me. Particularly since the time spent transferring the actual data only increased 10%, yet the latency increased 100%!
That feels... wrong... to me.
I found a few links here that were helpful (through Google no less!) ...
... but nothing authoritative.
So, is this normal? It doesn't feel normal. What is the "typical" latency I should expect when moving network packets from the east coast <--> west coast of the USA?
Speed of Light:
You are not going beat the speed of light as an interesting academic point. This link  works out Stanford to Boston at ~40ms best possible time. When this person did the calculation he decided the internet operates at about "within a factor of two of the speed of light", so there is about ~85ms transfer time.
TCP Window Size:
If you are having transfer speed issues you may need to increase the receiving window tcp size. You might also need to enable window scaling if this is a high bandwidth connection with high latency (Called a "Long Fat Pipe"). So if you are transferring a large file, you need to have a big enough receiving window to fill the pipe without having to wait for window updates. I went into some detail on how to calculate that in my answer Tuning an Elephant .
Geography and Latency:
A failing point of some CDNs (Content Distribtuion Networks) is that they equate latency and geography. Google did a lot of research with their network and found flaws in this, they published the results in the white paper Moving Beyond End-to-End Path Information to Optimize CDN Performance :
First, even though most clients are served by a geographically nearby CDN node, a sizeable fraction of clients experience latencies several tens of milliseconds higher than other clients in the same region. Second, we find that queueing delays often override the benefits of a client interacting with a nearby server.
Also if you start to study BGP (core internet routing protocol) and how ISPs choose peerings, you will find it is often more about finances and politics, so you might not always get the 'best' route to certain geographic locations depending on your ISP. You can look at how your IP is connected to other ISPs (Autonomous Systems) using a looking glass router . You can also use a special whois service :
whois -h v4-peer.whois.cymru.com "22.214.171.124" PEER_AS | IP | AS Name 25899 | 126.96.36.199 | LSNET - LS Networks 32869 | 188.8.131.52 | SILVERSTAR-NET - Silver Star Telecom, LLC
It also fun to explore these as peerings with a gui tool like linkrank , it gives you a picture of the internet around you. http://rescomp.stanford.edu/~cheshire/rants/Latency.html
This site  would suggest around 70-80ms latency between East/West coast US is typical (San Francisco to New York for example).
Trans-Atlantic Path NY 78 London Wash 87 Frankfurt
Trans-Pacific Path SF 147 Hong Kong
Trans-USA Path SF 72 NY
Here are my timings (I'm in London, England, so my West coast times are higher than East). I get a 74ms latency difference, which seems to support the value from that site.
NY - 108ms latency, 61ms transfer, 169 total OR - 182ms latency, 71ms transfer, 253 total
These were measured using Google Chrome dev tools. http://ipnetwork.bgtmo.ip.att.net/pws/network_delay.html
Measure with ICMP first if at all possible. ICMP tests typically use a very small payload by default, do not use a three-way handshake, and do not have to interact with another application up the stack like HTTP does. Whatever the case, it is of the utmost importance that HTTP results do not get mixed up with ICMP results. They are apples and oranges.
Going by the answer of Rich Adams  and using the site  that he recommended, you can see that on AT&T's backbone, it takes 72 ms for ICMP traffic to move between their SF and NY endpoints. That is a fair number to go by, but you must keep in mind that this is on a network that is completely controlled by AT&T. It does not take into account the transition to your home or office network.
If you do a ping against careers.stackoverflow.com from your source network, you should see something not too far off of 72 ms (maybe +/- 20 ms). If that is the case, then you can probably assume that the network path between the two of you is okay and running within normal ranges. If not, don't panic and measure from a few other places. It could be your ISP.
Assuming that passed, your next step is to tackle the application layer and determine if there is anything wrong with the additional overhead you are seeing with your HTTP requests. This can vary from app to app due to hardware, OS, and application stack, but since you have roughly identical equipment on both the East and West coasts, you could have East coast users hit the West coast servers and West coast users hit the East coast. If both sites are configured properly, I would expect to see all numbers to be more less equal and to therefore demonstrate that what you are seeing is pretty much par for the coarse.
If those HTTP times have a wide variance, I would not be surprised if there was a configuration issue on the slower performing site.
Now, once you are at this point, you can attempt to do some more aggressive optimization on the app side in order to see if those numbers can be reduced at all. For example, if your are using IIS 7, are you taking advantage of its caching capabilities, etc? Maybe you could win something there, maybe not. When it comes to tweaking low-level items such as TCP windows, I am very skeptical that it would have much of an impact for something like Stack Overflow. But hey - you won't know until you try it and measure. http://serverfault.com/questions/137348/how-much-network-latency-is-typical-for-east-west-coast-usa/137357#137357
I'm seeing consistent differences, and I'm sitting in Norway:
serverfault careers 509ms 282ms 511ms 304ms 488ms 295ms 480ms 274ms 498ms 278ms
This was measured with the scientific accurate and proven method of using the resources view of Google Chrome and just repeatedly refreshing each link.
Tracing route to serverfault.com [184.108.40.206] over a maximum of 30 hops: 1 <1 ms 1 ms <1 ms 220.127.116.11 2 2 ms 1 ms 1 ms qos-1.webhuset.no [18.104.22.168] 3 1 ms 1 ms 1 ms 22.214.171.124 4 1 ms 2 ms 1 ms 201.82-134-26.bkkb.no [126.96.36.199] 5 14 ms 14 ms 14 ms 188.8.131.52 6 13 ms 13 ms 14 ms TenGigabitEthernet8-4.ar1.OSL2.gblx.net [184.108.40.206] 7 22 ms 21 ms 21 ms te7-1-10G.ar3.cph1.gblx.net [220.127.116.11] 8 21 ms 20 ms 20 ms sprint-1.ar3.CPH1.gblx.net [18.104.22.168] 9 21 ms 21 ms 20 ms sl-bb20-cop-15-0-0.sprintlink.net [22.214.171.124] 10 107 ms 107 ms 107 ms 126.96.36.199 11 107 ms 106 ms 105 ms sl-bb20-msq-15-0-0.sprintlink.net [188.8.131.52] 12 106 ms 106 ms 107 ms sl-crs2-nyc-0-2-5-0.sprintlink.net [184.108.40.206] 13 129 ms 135 ms 134 ms sl-crs2-chi-0-15-0-0.sprintlink.net [220.127.116.11] 14 183 ms 183 ms 184 ms sl-crs2-chi-0-10-3-0.sprintlink.net [18.104.22.168] 15 189 ms 189 ms 189 ms sl-gw12-sea-2-0-0.sprintlink.net [22.214.171.124] 16 193 ms 189 ms 189 ms 126.96.36.199 17 181 ms 181 ms 180 ms core2-gi61-to-core1-gi63.silverstartelecom.com [188.8.131.52] 18 182 ms 182 ms 182 ms sst-6509b-gi51-2-gsr2-gi63.silverstartelecom.com [184.108.40.206] 19 195 ms 195 ms 194 ms sst-6509-peak-p2p-gi13.silverstartelecom.com [220.127.116.11] 20 197 ms 197 ms 197 ms ge-0-0-2-cvo-br1.peak.org [18.104.22.168] 21 188 ms 187 ms 189 ms ge-1-0-0-cvo-core2.peak.org [22.214.171.124] 22 198 ms 198 ms 198 ms vlan5-cvo-colo2.peak.org [126.96.36.199] 23 198 ms 197 ms 197 ms stackoverflow.com [188.8.131.52] Trace complete.
Tracing route to careers.stackoverflow.com [184.108.40.206] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 220.127.116.11 2 2 ms 1 ms <1 ms qos-1.webhuset.no [18.104.22.168] 3 1 ms 1 ms 1 ms 22.214.171.124 4 1 ms 1 ms 2 ms 201.82-134-26.bkkb.no [126.96.36.199] 5 12 ms 13 ms 13 ms 188.8.131.52 6 13 ms 14 ms 14 ms TenGigabitEthernet8-4.ar1.OSL2.gblx.net [184.108.40.206] 7 21 ms 21 ms 21 ms ge7-1-10G.ar1.ARN3.gblx.net [220.127.116.11] 8 21 ms 20 ms 20 ms tiscali-1.ar1.ARN3.gblx.net [18.104.22.168] 9 116 ms 117 ms 122 ms xe-4-2-0.nyc20.ip4.tinet.net [22.214.171.124] 10 121 ms 122 ms 121 ms peer1-gw.ip4.tinet.net [126.96.36.199] 11 * * * Request timed out.
Unfortunately, it now starts going into a loop or whatnot and continues giving stars and timeout until 30 hops and then finishes.
Note, the traceroutes are from a different host than the timings at the start, I had to RDP to my hosted server to execute them
Several of the answers here are using ping and traceroute for their explanations. These tools have their place, but they are not reliable for network performance measurement.
In particular, (at least some) Juniper routers send processing of ICMP events to the control plane of the router. This is MUCH slower than the forwarding plane, especially in a backbone router.
There are other circumstances where the ICMP response can be much slower than a router's actual forwarding performance. For instance, imagine an all-software router (no specialized forwarding hardware) that is at 99% of CPU capacity, but it is still moving traffic fine. Do you want it to spend a lot of cycles processing traceroute responses, or forwarding traffic? So processing the response is a super low priority.
As a result, ping/traceroute give you reasonable upper bounds but they don't really tell you how fast things are going.
Here's an example traceroute from the University of Michigan (central US) to Stanford (west coast US). (It happens to go by way of Washington, DC (east coast US), which is 500 miles in the "wrong" direction.)
% traceroute -w 2 www.stanford.edu traceroute to www-v6.stanford.edu (188.8.131.52), 64 hops max, 52 byte packets 1 * * * 2 * * * 3 v-vfw-cc-clusta-l3-outside.r-seb.umnet.umich.edu (184.108.40.206) 3.808 ms 4.225 ms 2.223 ms 4 l3-bseb-rseb.r-bin-seb.umnet.umich.edu (220.127.116.11) 1.372 ms 1.281 ms 1.485 ms 5 l3-barb-bseb-1.r-bin-arbl.umnet.umich.edu (18.104.22.168) 1.784 ms 0.874 ms 0.900 ms 6 v-bin-arbl-i2-wsu5.wsu5.mich.net (22.214.171.124) 2.443 ms 2.412 ms 2.957 ms 7 v0x1004.rtr.wash.net.internet2.edu (126.96.36.199) 107.269 ms 61.849 ms 47.859 ms 8 ae-8.10.rtr.atla.net.internet2.edu (188.8.131.52) 28.267 ms 28.756 ms 28.938 ms 9 xe-1-0-0.0.rtr.hous.net.internet2.edu (184.108.40.206) 52.075 ms 52.156 ms 88.596 ms 10 * * ge-6-1-0.0.rtr.losa.net.internet2.edu (220.127.116.11) 496.838 ms 11 hpr-lax-hpr--i2-newnet.cenic.net (18.104.22.168) 76.537 ms 78.948 ms 75.010 ms 12 svl-hpr2--lax-hpr2-10g.cenic.net (22.214.171.124) 82.151 ms 82.304 ms 82.208 ms 13 hpr-stanford--svl-hpr2-10ge.cenic.net (126.96.36.199) 82.504 ms 82.295 ms 82.884 ms 14 boundarya-rtr.stanford.edu (188.8.131.52) 82.859 ms 82.888 ms 82.930 ms 15 * * * 16 * * * 17 www-v6.stanford.edu (184.108.40.206) 83.136 ms 83.288 ms 83.089 ms
In particular, note the time difference between the traceroute results from the wash router and the atla router (hops 7 & 8). the network path goes first to wash and then to atla. wash takes 50-100ms to respond, atla takes about 28ms. Clearly atla is further away, but its traceroute results suggest that it's closer.
See http://www.internet2.edu/performance/ for lots of info on network measurement. (disclaimer, i used to work for internet2)
To add some specific relevance to the original question... As you can see I had an 83 ms round-trip ping time to stanford, so we know the network can go at least this fast.
Note that the research & education network path that I took on this traceroute is likely to be faster than a commodity internet path. R&E networks generally overprovision their connections, which makes buffering in each router unlikely. Also, note the long physical path, longer than coast-to-coast, although clearly representative of real traffic.
michigan->washington, dc->atlanta->houston->los angeles->stanford
I see approx 80-90ms latency on well run, well measured links between East and West coasts.
It would be interesting to see where you're gaining latency - try a tool like layer-four traceroute (lft). Chances are a lot of it is gained on the "last mile" (i.e. in your local broadband provider).
That the transfer time was only slightly impacted is to be expected - packet loss and jitter are more useful measurements to look at when investigating transfer time differences between two locations.
Just for fun, when I played the online game Lineage 2 NA release from within Europe:
Response time to east coast servers: ~110-120ms Response time to west coast servers: ~190-220ms
The difference seems to support that up to 100ms is within reason, considering the unpredictable nature of the internet.
Using the acclaimed Chrome refresh test, I get document load time that differs with roughly 130ms.
NY OR 109ms 271ms 72ms 227ms 30ms 225ms 33ms 114ms 34ms 224ms
Using Chrome, on a residential connection.
Using lft from a VPS in a datacenter in Newark, New Jersey:
terracidal ~ # lft careers.stackoverflow.com -V Layer Four Traceroute (LFT) version 3.0 Using device eth0, members.linode.com (220.127.116.11):53 TTL LFT trace to 18.104.22.168:80/tcp 1 22.214.171.124 0.4/0.5ms 2 vlan804.tbr2.mmu.nac.net (126.96.36.199) 0.4/0.3ms 3 0.e1-1.tbr2.tl9.nac.net (188.8.131.52) 1.3/1.5ms 4 nyiix.Peer1.net (184.108.40.206) 1.4/1.4ms 5 oc48-po3-0.nyc-75bre-dis-1.peer1.net (220.127.116.11) 1.6/1.5ms 6 18.104.22.168 2.7/2.2ms 7 22.214.171.124 2.3/1.8ms 8 [target open] 126.96.36.199:80 2.5ms terracidal ~ # lft serverfault.com -V Layer Four Traceroute (LFT) version 3.0 Using device eth0, members.linode.com (188.8.131.52):53 TTL LFT trace to stackoverflow.com (184.108.40.206):80/tcp 1 220.127.116.11 36.4/0.6ms 2 vlan803.tbr1.mmu.nac.net (18.104.22.168) 0.4/0.4ms 3 0.e1-1.tbr1.tl9.nac.net (22.214.171.124) 1.3/1.4ms 4 nyk-b3-link.telia.net (126.96.36.199) 1.6/1.4ms 5 nyk-bb2-link.telia.net (188.8.131.52) 1.9/84.8ms 6 nyk-b5-link.telia.net (184.108.40.206) 1.7/1.7ms 7 220.127.116.11 2.1/2.1ms 8 cr1.n54ny.ip.att.net (18.104.22.168) 83.5/83.6ms 9 cr2.cgcil.ip.att.net (22.214.171.124) 82.7/83.1ms 10 cr2.st6wa.ip.att.net (126.96.36.199) 83.4/83.5ms 11 cr2.ptdor.ip.att.net (188.8.131.52) 82.7/82.7ms 12 gar1.ptdor.ip.att.net (184.108.40.206) 82.2/82.3ms 13 220.127.116.11 82.9/82.8ms 14 sst-6509b-gi51-2-gsr2-gi63.silverstartelecom.com (18.104.22.168) 84.1/84.0ms 15 sst-6509-peak-p2p-gi13.silverstartelecom.com (22.214.171.124) 83.3/83.4ms 16 ge-0-0-2-cvo-br1.peak.org (126.96.36.199) 86.3/86.2ms ** [neglected] no reply packets received from TTLs 17 through 18 19 [target closed] stackoverflow.com (188.8.131.52):80 86.3/86.3ms