Re: Performance Checking

by "Bryan Bateman" <batemanb(at)home.com>

 Date:  Fri, 17 Mar 2000 09:16:57 -0500
 To:  <moe(at)maxim-ic.com>
 Cc:  <hwg-servers-digest(at)mail.hwg.org>
  todo: View Thread, Original
I think you may want to examine the performance of the routes.

Look at the traceroute below.  Seems like a lot of hops to me.  Also note
that network response times go up by a factor of 4 on the exodus.net
network.  I recommend having someone check this during peak traffic times.
You will probably see worse bottlenecking than you see here.

You also mentioned co-location.  Is this being accomplised by hardware at
exodus.net's site or DNS round-robin.  Compare an nslookup of your site to
that of microsoft below.

As you can see, you are resolving to only one IP while microsoft
round-robins to multiple IP addresses.

Is there a network segment between exodus.net and your site?  That is the
only way I can see co-location occuring.  If so, you probably want to
examine that network segment as well.

All Internet traffic "appears" to be going to one location.

If they are using hardware, chances are it is diverting client traffic by IP
address.  If the clients that browse the pages are from sizeable businesses
and they have proxy servers to the Internet, then you may see "pooling" to
one server instead of an even distribution across all servers.  BTW, cable
modem providers use proxy servers as well.

Check the web logs of all servers to see if  there is an equal distribution.

I hope this helps.
----------------------------------------------------------------------------
---------------------------------------

C:\>tracert www.maxim-ic.com

Tracing route to www.maxim-ic.com [209.1.238.246]
over a maximum of 30 hops:

  1    16 ms    15 ms    16 ms  24.2.41.1
  2   <10 ms    16 ms   <10 ms  10.0.191.1
  3   <10 ms    16 ms    16 ms  10.0.188.1
  4   <10 ms    15 ms   <10 ms  c1-pos5-0.nrflva1.home.net [24.7.73.109]
  5   <10 ms   <10 ms    16 ms  c1-pos3-1.washdc1.home.net [24.7.68.118]
  6    16 ms    15 ms    16 ms  bb1-se4-1-0.exds-dc.nap.home.net
[24.7.73.94]
  7    16 ms    15 ms    16 ms  ibr01-f11-0-0.hrnd01.exodus.net
[209.185.249.105
]
  8    15 ms    16 ms    16 ms  dcr04-p0-1.hrnd01.exodus.net
[216.33.203.149]
  9    15 ms    16 ms    16 ms  bbr02-g4-0.hrnd01.exodus.net
[216.33.203.126]
 10    78 ms    93 ms    79 ms  bbr02-p5-0.sntc02.exodus.net [216.32.173.13]
 11    78 ms    78 ms    94 ms  bbr01-g3-0.sntc02.exodus.net
[216.33.154.131]
 12    78 ms    94 ms    78 ms  bbr01-p5-0.sntc01.exodus.net
[209.185.249.109]
 13    94 ms    94 ms    78 ms  dcr03-g6-0.sntc01.exodus.net [216.33.147.1]
 14    78 ms    94 ms    78 ms  rsm02-vlan919.sntc01.exodus.net
[216.33.147.170]

 15   172 ms    94 ms    93 ms  209.1.238.246

Trace complete.

----------------------------------------------------------------------------
-------------------------------------

C:\>nslookup maxim-ic.com
Server:  proxy2.nwptn1.va.home.com
Address:  24.2.48.34

Non-authoritative answer:
Name:    maxim-ic.com
Address:  209.1.238.246


C:\>nslookup microsoft.com
Server:  proxy2.nwptn1.va.home.com
Address:  24.2.48.34

Non-authoritative answer:
Name:    microsoft.com
Addresses:  207.46.130.14, 207.46.130.149, 207.46.130.45, 207.46.131.137
          207.46.131.30

HWG: hwg-servers mailing list archives, maintained by Webmasters @ IWA