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 a dedicated server running on Plesk Panel for Windows. The server has 8GB ram and seems to be getting slower due to high connection queue I think.

I'm running 8GB RAM on Quad-Core AMD Opteron(tm) Processor 1354.

Other than adding more hardware, what are some of the ways to improve response times and/or monitor what is causing the bottleneck?

Right now many sites on the default pool, when I load them up, are getting stuck at the "waiting for reply". Often times websites will take 10 seconds to respond.

I've been recommended to give each website its own dedicated application pool. However I do have about 350 sites on the server. With this amount of memory, do you recommend using this method to make the server run faster? Would it run out of memory with only 8GB RAM?

share|improve this question

1 Answer 1

Make Better Websites

You can improve your websites. You can use tools like firebug, yslow or fiddler to determine what content or request is slowing the site. Also take a look at some best practices. This is usually the best solution in lieu of more hardware.

Refs:

Yahoo Best Practices

Firebug for Firefox

YSlow for Firebug

Fiddler for Everything

Monitor Hardware Performance

On the server side you can take a look at performance monitoring to see if the slowdown is isolated at a specific hardware component such as disk writes/ques, processor, memory or network interfaces.

Used Dedicated Application Pools

I do recommend using dedicated application pools for each site. This way you can either monitor the usage of each pool to help find the culprit and/or restrict processor usage.

share|improve this answer
    
The issue here isn't site optimization, it's server optimzation. I host hundreds of sites. The request queue is too long. –  Kenny Jul 4 '10 at 6:06
    
Well if it really is the request queue and nothing else then just change the application pool queue-length limit to something manageable so your server doesn't get bogged down. This is all in the application pool properties of IIS. Just remember that requests that go over this limit will get a 503 error. –  James Santiago Jul 4 '10 at 7:59

Your Answer

 
discard

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