Corey Hudson wrote: > The last several weeks we have had customers complain that they are > experiencing trouble accessing our website. That it is slow. I know this > is a network problem since locally the website is fast and the CPU usage on > our servers are showing 1% utilization. So, some of the things I do to > resolve the problem is to try and access their website, I also have them > perform a trace route. And now, I have found a company near us that has an > ip address very close to ours. (within the same class D network and pinging > them turned around a quick response). So, I thought if I had our > customers access this other website at the same time they are having > problems with ours, that it would narrow it down to a network problem. > > Besides these things, is there any thing else I could do? I would like > some hard evidence to present to my ISP. I also don't expect my customers > to help me debug this problem.
Grab the entire home-page of your website using a browser like Firefox, and look at the size of the resultant files. Now, at 10 bits per byte (to count for overhead, seems to be a pretty accurate guestimate), figure out how long it would take to transfer that page to your remote site with the uplink you have. Compare to what it is actually taking. You may have no network problem at all, but rather an over-clever web designer who has no idea that all that cute flash and graphics and stuff doesn't look nearly as good across the 'net as it does locally. If that's not your problem, it's really pretty simple to just test your uplink speed and compare to what you are paying for. SCP, FTP, or even one of the many link speed test sites will quickly tell you if you are getting what you are paying for. Nick. ------------------------------------------------------ To unsubscribe: [EMAIL PROTECTED] For additional commands: [EMAIL PROTECTED] Archive: http://archives.gnatbox.com/gb-users/
