Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have recently upgraded our server to a new server (2-12core AMD CPUs, 12Gb Ram, windows server 2008, exchange 2010) and I run a company web app using IIS and PHP/MySQL. The server gets really slow occasionally (loading pages on the web app) but I don't know how to find out if it's the network, server hardware, IIS, PHP or MySQL causing the problem. What is the best way to determine where the bottleneck is?

share|improve this question

migrated from stackoverflow.com Aug 30 '11 at 14:56

This question came from our site for professional and enthusiast programmers.

    
I just noticed there was about 5 IIS worker processes, one of which was gathering memory at over 500k already. When I tried to Stop the web server in IIS it wouldn't stop (to the point I could click start) until I manually ended that one worker process, the other worker processes closed when I clicked Stop. –  Evan4623 Aug 30 '11 at 14:44
    
I should also mention I never had this problem in windows server 2003 before I upgraded. Seems to be something with IIS7 worker processes. –  Evan4623 Aug 30 '11 at 15:09
    
"The site gets slow occasionally" is not a helpful problem description -- You need to do some more digging on your own to determine where the bottleneck is in order for us to be able to help you, otherwise you'll just be getting wild-ass guesses. Things to check: CPU Load/Utilization, Memory/Swap utilization, Disk Utilization, External Resources (databases, etc.), site usage patterns (this happen during peak load periods?). –  voretaq7 Aug 30 '11 at 15:14
    
The question was how do I find the bottleneck, and you're asking me to determine where the bottleneck is so you can help me? I'm not sure I understand what you mean. I'm just trying to identify the cause of the problem, but I don't know how to go about tracking it down. –  Evan4623 Aug 30 '11 at 15:35
1  
We cannot find the bottleneck for you: We do not have access to your system, and we do not know what software you are running. You must track down a probable cause (by checking the things I indicated (and others that may occur to you as you investigate), and by using your own common sense / knowledge of your environment. If you tell us what you see we can try to help you understand what it means, and the more relevant details you can provide the more likely it is that we can help you. –  voretaq7 Aug 30 '11 at 15:46
show 2 more comments

Your Answer

 
discard

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

Browse other questions tagged or ask your own question.