Text 42713, 88 rader
Skriven 2008-02-06 11:15:51 av Jeff Guerdat (1:123/789.0)
  Kommentar till text 42706 av JEAN PARROT (1:123/140)
Ärende: LAN uses.
=================
JEAN PARROT -> JEFF GUERDAT wrote:

 JG>> WHat the real-life comparison is, I don't know.  I
 JG>> can say that 100Mb Ethernet has given me a max of about 8MB/sec in
 JG>> real  life (using ftp to transfer a file with as little overhead as
 JG>> possible).

 JP>         My use of the LAN here is very casual, I at times, will copy
 JP>    one small file from one to tother, time spend is immaterial. What I
 JP>    noticed though, is the rate shown when D/Ling drivers or what have
 JP>    you from different sites. Some are around 200/s as others are 80/s.
 JP>    I fancy that is due to the source not me. These are bits.

Those would be kbytes or you'd still be waiting for those files.  ;)

And you never know where the slowness is.  I tend to doubt it's the servers
themselves but some other place in the World Wide Wait.  You've heard me talk
about it before - use "traceroute" to see what's going on if you're bored.  It
basically does a ping for each hop (each router is a hop) to determine what
latency exists where in the connection (assuming it takes the same path as your
download, which isn't guaranteed).  Here's a sample: from Linux - use tracert
from Windows:

[jguerdat@toshiba ~]$ traceroute windowsupdate.microsoft.com
traceroute to windowsupdate.microsoft.com (207.46.225.221), 30 hops max, 40
byte packets
 1  192.168.0.1 (192.168.0.1)  3.821 ms  5.358 ms  10.112 ms
 2  10.108.160.1 (10.108.160.1)  500.789 ms  501.216 ms  501.615 ms
 3  gig1-1.rochnybtn-rtr01.nyroc.rr.com (24.93.0.217)  499.561 ms 500.150 ms 
509.574 ms
 4  srp7-0.rochnymth-rtr04.nyroc.rr.com (24.93.3.118)  511.932 ms 512.019 ms 
512.106 ms
 5  srp12-0.rochnymth-rtr02.nyroc.rr.com (24.93.4.250)  510.323 ms 511.378 ms 
521.813 ms
 6  so-1-2-2.syrcnycsr-rtr03.nyroc.rr.com (24.24.7.62)  522.730 ms 496.531 ms 
17.377 ms
 7  te-3-2.car2.Cleveland1.Level3.net (64.156.66.41)  20.608 ms  26.235 ms
te-3-1.car2.Cleveland1.Level3.net (4.78.59.45)  26.631 ms
 8  ae-6-6.ebr2.Chicago1.Level3.net (4.69.132.202)  35.164 ms  37.913 ms 
38.869 ms
 9  ae-78.ebr3.Chicago1.Level3.net (4.69.134.62)  46.292 ms  45.786 ms  497.478
ms
10  ae-3.ebr2.Denver1.Level3.net (4.69.132.61)  515.492 ms  515.551 ms 513.854
ms
11  ae-2.ebr2.Seattle1.Level3.net (4.69.132.53)  539.362 ms  610.509 ms 
611.564 ms
12  ge-2-0-0-56.gar1.Seattle1.Level3.net (4.68.105.169)  595.992 ms
ge-2-0-0-54.gar1.Seattle1.Level3.net (4.68.105.105)  490.581 ms
ge-2-0-0-52.gar1.Seattle1.Level3.net (4.68.105.41)  503.537 ms
13  65.59.235.6 (65.59.235.6)  502.696 ms  503.841 ms  519.270 ms
14  ge-5-2-0-55.tuk-64cb-1b.ntwk.msn.net (207.46.41.53)  517.879 ms 518.266 ms 
518.666 ms
15  ten2-3.tuk-76c-1a.ntwk.msn.net (207.46.35.73)  519.522 ms  521.950 ms 
521.451 ms
16  po16.tuk-65ns-mcs-1b.ntwk.msn.net (207.46.35.142)  578.997 ms 579.568 ms 
494.790 ms

You want to see no more than double digits (10-90) millisecond response times. 
Note that many of these are 500+ ms due to my uploading of a large file right
at this moment.  That would make any transfers very slow.  Normally, you
wouldn't see this but you would see one or two places which are slow - those
are the places of congestion/slowness. While the names of the routers are very
offbeat, you can frequently guess where they are geographically by using some
imagination in decoding them.  nyroc.rr.com sounds like Rochester, NY and guess
what Chicago/Denver/Seattle might represent?

Just trying to expand your horizons beyond your little domain...  <smile>

 JP>         What dazzles me is the old Win98SE Thinkpad. It reduses to
 JP>    honour a WiFi card. I can only insert a Dlink 650 in it, any other
 JP>    card will not go home to the connector, it has a larger key on the
 JP>    connector end that prevents pushing it all the way. Looking at the
 JP>    connector end, with the card upright, it is on the right side. The
 JP>    Dlink driver is loaded but will not run. I checked the IRQ, no
 JP>    conflict.

I'll wager that's because the card is a Cardbus and/or 3.3v and you're trying
to put it into a slot that's PCMCIA-only and/or 5v.  It's physically blocked to
prevent possible damage to the card and laptop...

-- 
Jeff Guerdat

"I feel so miserable without you, it's almost like having you here."
                                                      Stephen Bishop

--- Thunderbird 2.0.0.9 (X11/20071115)
 * Origin: The Eastern Star - Fidonet Via Your Newsreader (1:123/789.0)