Web server performance metrics

You run each website as a different process and govern the process and the resources it uses (perhaps alotted servers wasn't the best phrase, resources would of been better).

Without doing this you will cause performance issues for customers other than the one with the large site.
 
9000 customers over 40 servers? Thats over 200 customers per server?

Their numbers don't match up.
Why not? My shop generates oner page view every 10 seconds during peak times, and it's one of their bigger / busier sites. But let's suppose it were typical. Then 200 sites on one server would be requiring 20 page views per second. I can easily believe that a serious server could cope with that. Can't you?

(In fact, EKM don't manage things quite like that. They have a couple of dozen "very large" clients with VPS solutions. Then they have about 50 "large" clients on one server - the one I'm on. They have a bunch of servers for "medium" clients, averaging about 200-250 per server. And they have a bunch of servers for "small" clients, averaging about 500 per server.)

It all seems quite believable to me.

As I've said, I think the issue they've discovered is that something is dragging down the performance of their "large clients" server. Given its specs, it ought to cope with the workload - but it isn't coping.
 
Ahh, ok, that makes a bit more sense.

What CPU and RAM does the server have?

Find out the hard disk setup on the server, that will be the first place to start for the performance issues (it nearly always is).
 
Dale_d3100 said:
What CPU and RAM does the server have?

I don't know and I don't care. Optimizing its performance isn't my job.
 
Back
Top