Re: [Debian-NYC] debugging network slowness

On Thu, Dec 16, 2010 at 9:31 AM, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:

On 12/16/2010 12:36 AM, Brian Gupta wrote:
> On Wed, Dec 15, 2010 at 4:57 PM, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:

>> * wget takes far too long to do something as simple as loading an http
>> redirect. (15 seconds just to fetch the redirect from
>> http://nytimes.com/ to http://www.nytimes.com/)
>>
>> * DNS on its own does not seem to be the problem: directly querying the
>> local nameservers with dig returns results very quickly (~0.02 to 0.04
>> seconds), and all three nameservers in resolv.conf are at comparable speeds.
>>
>> * TCP connections on their own do not seem to be the problem: using
>> netcat to connect to the times' site and fetch the same 302 redirect is
>> also trivially quick (less than a tenth of a second)
>

> Stupid question, has anyone thought to run traceroute while there are
> megaslow network conditions? (My apologies if so, as I haven't been
> following closely.)

it's not a stupid question. But as you can see from the notes above,
DNS on its own and TCP on its own are *not* mega-slow. This is what has
me stumped.

But sure, a traceroute wouldn't hurt.

Here's what i get to the test server we've been using:

>>> 0 dkg@pip:~$ traceroute nytimes.com
>>> traceroute to nytimes.com (199.239.136.200), 30 hops max, 60 byte packets
>>> 1 splat.lair.fifthhorseman.net (192.168.13.1) 0.479 ms 0.384 ms 0.346 ms
>>> 2 er1.nyc1.speakeasy.net (216.254.115.1) 10.477 ms 13.184 ms 18.252 ms
>>> 3 110.ge-0-0-0.cr1.nyc1.speakeasy.net (69.17.83.213) 20.059 ms 20.518 ms 20.890 ms
>>> 4 444.ge-3-3-0.mpr1.lga3.us.above.net (208.184.48.178) 15.247 ms 15.931 ms 17.337 ms
>>> 5 above-qwest.lga5.us.above.net (64.125.13.246) 18.301 ms 18.992 ms 21.435 ms
>>> 6 * * *
>>> 7 nyc-edge-03.inet.qwest.net (205.171.217.26) 25.186 ms 8.844 ms 10.333 ms
>>> 8 * * *
>>> 9 * * *
>>> 10 * * *
>>> 11 * * *
>>> 12 * * *
>>> 13 * * *
>>> 14 * * *
>>> 15 * * *
>>> 16 * * *
>>> 17 * * *
>>> 18 * * *
>>> 19 * * *
>>> 20 * * *
>>> 21 * * *
>>> 22 * * *
>>> 23 * * *
>>> 24 * * *
>>> 25 * * *
>>> 26 * * *
>>> 27 * * *
>>> 28 * * *
>>> 29 * * *
>>> 30 * * *
>>> 0 dkg@pip:~$

Steve, what do you see when you're using one of the networks on which
iceweasel gives you trouble?

--dkg

_______________________________________________
DebianNYC mailing list
DebianNYC@vireo.org
http://lists.vireo.org/cgi-bin/mailman/listinfo/debiannyc