Cliff,
I'm sending you by e-mail (don't think I can attach a graphics file here) the doc proof that the problem lies between Atlanta and Ft Lauderdale. This was an attempt to trace your routing. From Cyprus, it crossed the Atlantic by West Orange. Unfortunately, this time it happened to land onto the AT network in NY which is often overloaded. It managed to find a routing to Atlanta after three attempts in different directions. The one it finally found pinged at 277 ms, which is not bad for a daytime peak hour transatlantic connection. It then found the Florida spur and pinged at 287 ms. It then took 6 attempts to home in on your server, 2 of which were fatal timeouts at 1200 ms, taking a total of 3.6 seconds, just for a single 58 byte ping to effectively travel from Atlanta and back.
In my testing over the past three days, I repeatedly obtained similar or worse results. Using a ping programme, I obtained 10/10 timeouts several times, 7/10 being about the average. No matter the routing before Atlanta, the Trace programme always showed the timeouts between there and FL.
Server speed is meaningless if the bandwidth is restricted, as seems to be the case here. Yoou would not get better results with a dedicated Cray as a server (if it were possible!)
Best regards
Brian
| Brian, | | Thanks for your concern, and maybe there is fear that we are trying to mislead people, which is not true. | | We do not have the server in house here in Portland, Maine. It is in Fort Lauderdale, Florida, at Advances.com. | | We are sharing a network with I don't know how many servers, and our computer server (Dual P3 550, 512M ram) is shared with 2 other websites on it. The server is running NT Server, Access, and Cold Fusion. The network is on a T3 hub that gives us speeds up to 80KB/s (20 times faster than a 56K modem). The old server had 50 websites on it, and was a Dual P2-450. | | The reason I put the net tools in the previous response, is so that users can provide me with information so that I can fix the problems, if they exist. What I need is some evidence of a problem. By saying, "I cannot connect" or "something didn't work" is not very helpful to me, because I have nothing to work with. | | Also, the server is still being configured/optimized. The Cold Fusion server goes down more frequent than we prefer, but it seems to be getting better. The Cold Fusion server, seems to "stall" when a heavily computational task is run. When the Cold Fusion server goes down, the web server is still up, and can be pinged. It takes about 5-7 minutes to restart the Cold Fusion Server. We are working on a solution there. | | The fact is that we get high speeds here all the time, and across 3000 miles. Many problems can occur for individuals like network congestion or limits to phone lines, etc. | | If pages are too large, I want to know which ones, so I can "trim" it down, if possible. We do have criteria that we try to meet, and to stay within 100K for the total page is one of them. | | We want to help in anyway we can. It's in our best interest to provide the best service we can. | | Thanks, | Cliff | |
reply »