Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I ran a 'yum update' on a CentOS based web server. Kernel version stayed the same at It upgraded a bunch of stuff, including - mysql from 5.0.45 to 5.0.91 apache from 2.2.3 to 2.2.15

I'm finding that my server response time is quite degraded. Web requests that would have completed in .5 seconds are taking over a second. My configuration files for both Apache and Mysql haven't changed.

I'm running on EC2, so I can run the old image and compare. Server processes appear to be the same.

Where should I look first to find out where the kink in the pipe is?

share|improve this question
How do you know that server response time as degraded from .5 seconds to over a second? Is this from a client or server perspective? My answer assumes it is from the server perspective ... – Kyle Brandt Jun 22 '10 at 13:15
It's page delivery to a sister server - also running in the same EC2 area - running ab. I'm comparing results of ab test before and after. – Laizer Jun 22 '10 at 13:20
In that case I would repeat the ab tests on the old and new versions from the server itself (not the sister server) and see if you still see a difference and go from there. – Kyle Brandt Jun 22 '10 at 13:28
The theme here is to localize the problem as much as possible. This is like like what you might do with debugging code -- Remove sections of code if you can to see if that fixes the problem to find out where it is exactly. – Kyle Brandt Jun 22 '10 at 13:29
up vote 2 down vote accepted

I would start my finding out if the problem is in Apache or if the problem is in MySQL. To do this with Apache you can look at Apache response times in ms with the %...D option in mod_log_config. For MySQL you can monitor queries times. The Slow Query Log is one way to do this for MySQL. Another way to see if it is MySQL from a more front-end standpoint is to see if Apache is slow serving out static content only. If one of these is taking longer than you would expect than you know where to go from there.

You can also of course check out system resource utilization with tools like top, vmstat, and iostat. Lastly, you might also have update your language modules (ie mod_php) and your problem could be there as well (or even network issues etc).

share|improve this answer
This was helpful. After searching for a good couple hours, I found that it was an eaccelerator installation that was compiled for a later version of PHP than what I had. Once I isolated it to a server (And not network) issue, I should have started by looking at the startup logs of Apache and Mysql. Once I did that, it was pretty clear what was happening. – Laizer Jun 24 '10 at 10:23

The problem could be also DNS (internal/lan) related.

What happen if you do a request from server itself (localhost)?

How apache (php or other...) does connect to mysql (localhost, ip, hostname...)?

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.