[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Master is still *really* slow:-/



On Wed, Nov 04, 1998 at 12:18:00PM -0800, Philippe Troin wrote:
."Steve Lamb" <morpheus@teleute.ml.org> writes:
.
.> On Wed, 4 Nov 1998 11:01:22 -0800, David Welton wrote:
.> 
.> >Here is the traceroute, if anyone has any comments...:
.> > 9  sl-bb2-stk-4-0-45M.sprintlink.NET (144.228.10.109)  68.18 ms
.> >54.262 ms  77.786 ms
.> >10  sl-bb22-stk-3-2.sprintlink.NET (144.232.4.9)  458.574 ms  280.389
.> >ms *
.> >11  sl-bb10-fw-0-0.sprintlink.NET (144.232.8.69)  382.969 ms  360.407
.> 
.>     68ms to 360ms in two hops internal to sprintlink.  Nope, not much you can
.> do.  Sprintlink is notorious for slowdowns like that.  Sprint and UU.  Hate
.> 'em both.
.
.8< snip
.
.Well, I don't go through sprintlink at all *and* I have a lot of
.packet loss...
.
.For comparison:
.                                            Packets            Pings
.Hostname                                 %Loss  Rcv Snt  Best  Avg  Worst
. 1. tantale.fifi.org                        0% 101 101    0    1      4
. 2. sjw-pm3-01.blueneptune.com              0% 101 101  145  155    231
. 3. sjw-t1-01.blueneptune.com               0% 101 101  131  154    198
. 4. main-106.sjc.above.net                  0% 101 101  143  199    798
. 5. core2-main.sjc.above.net                0% 100 101  140  162    387
. 6. savvis-above-45Mbps.sjc.above.net       0% 100 100  140  158    278
. 7. atm9-0-031.CR-1.DllsTX.savvis.net       6%  94 100  186  219    603
. 8. IGLOBAL-1.DllsTX.savvis.net             8%  92 100  187  195    244
. 9. master.debian.org                       7%  93 100  189  201    407
.
.IMHO, savvis is the culprit. The problem started when master started
.using savvis too...
.
.BTW, thanks for the nice mtr tip :-)
.
.Phil.

gentleman,

the statistics your are providing, as well as your complaints :>, are
exactly what i need to take to the table when i confront(?) our ISP
and Savvis regarding this issue.

as far as i am concerend you are my "customers" and as a customer
you deserve to have your concerns addressed and acted upon.

if you/i/we can continue to collect a few more traceroute/ping reports
( if only to provide a chronological record ) and complaints :o
i will happily request that our ISP and Savvis investigate the
cause of packet loss and link degradation.

f.t.r. UUnet, probably has some of the best customer service i have
encountered and we Never had connectivity problems when they were
our provider. as a matter of fact, in the 2.x years i have been at
Novare our link never failed once while UUnet was out upstream 
provider. 

thx,

mark

-- 

Horseman of the Digital Apocolypse


Reply to: