Running a tracert is probably a waste of time, the lag is almost never correlated with actual connectivity problems. Whatever is causing the server to be so slow appears to be within the server itself. We can connect TO the server quickly enough, but once there our packets need an excessively long time to trigger a response. Maybe the server farm operator periodically runs some housekeeping apps on S1 that are sapping its cpu cycles and slowing down response time. Whatever its source, the lag problem doesn't seem to be as bad as it was some months ago. The server is now downright fast at times and the lag storms are less common, but the problem still occurs and still seems specific to S1 and not present on S2.
Last edited by Jimcav; 11-10-2009 at 11:11 AM..
|