Reply to thread

Message

<blockquote data-quote="RocketCowboy" data-source="post: 494189" data-attributes="member: 25095">Traceroute (and Microsoft's not quite standard version tracert) basically step through the network path by sending a packet that will &quot;time out&quot; at the next step in the chain in order to trigger a response. That's where the time samples in the output come from ... the time between when the packet was sent and when the response was received. The &quot;request timed out&quot; simply means that the device that should have sent an error on the timed out packet did not respond. There are lots of valid reasons for that to happen, so in itself since the rest of the path works that's probably not an issue.Overall response times on the traceroute don't exceed 31ms, so I don't suspect it to be a network issue to the main server.I have noticed that at the bottom of each page, the stats indicate MySQL is taking between 8-15%. My suspicion is that MySQL is overloaded and adding the delay to the page loads. That's just my guess, without seeing the back end server load, but those SQL dips would effect every page and would not show up as a problem on network traces. The MySQL server might also be running on it's own server and not collocated on the web server, making the network tracing less conclusive.</blockquote>

[QUOTE="RocketCowboy, post: 494189, member: 25095"] Traceroute (and Microsoft's not quite standard version tracert) basically step through the network path by sending a packet that will "time out" at the next step in the chain in order to trigger a response. That's where the time samples in the output come from ... the time between when the packet was sent and when the response was received. The "request timed out" simply means that the device that should have sent an error on the timed out packet did not respond. There are lots of valid reasons for that to happen, so in itself since the rest of the path works that's probably not an issue. Overall response times on the traceroute don't exceed 31ms, so I don't suspect it to be a network issue to the main server. I have noticed that at the bottom of each page, the stats indicate MySQL is taking between 8-15%. My suspicion is that MySQL is overloaded and adding the delay to the page loads. That's just my guess, without seeing the back end server load, but those SQL dips would effect every page and would not show up as a problem on network traces. The MySQL server might also be running on it's own server and not collocated on the web server, making the network tracing less conclusive. [/QUOTE]

Verification