Apache KeepAlive on API Server

I have a LAMP server (Quad Core Debian with 4GB RAM, Apache 2.2 and PHP 5.3) with Rackspace which is used as an API Server. I would like to know what is the best KeepAlive option for Apache given our setup.

• The API server hosts a single PHP file which responds with plain JSON. This is a fairly hefty file which performs some MySql reads/writes and quite a few Memcache lookups.
• We have about 90 clients that are logged into the system at any one time.
• Roughly 1/3rd of clients would be idle.
• Of the active clients (roughly 60) they send a request to the API every 3 seconds.
• Clients switch from active to idle and vice versa every 15 or 20 minutes or so.

With KeepAlive On, the server goes nuts and memory peaks at close to 4GB (swap is engaged etc). With KeepAlive Off, the memory sits at 3GB however I notice that Apache is constantly killing and creating new processes to handle each connection.

So, my three options are:

1. KeepAlive On and KeepAliveTimeout Default - In this case I guess I will just need to get more RAM.

2. KeepAlive On and KeepAliveTimeout Low (perhaps 10 seconds?) If KeepAliveTimeout is set at 10 seconds, will a client maintain a constant connection to that one process by accessing the resource at regular 3 second intervals? When that client becomes idle for longer than 10 seconds will the process then be killed? If so I guess option 2 looks like the best one to go for?

3. KeepAlive Off This is clearly best for RAM, but will it have an impact on the response times due t开发者_如何学Goo the work involved in setting up a new process for each request?

Which option is best?

It looks like your php script is leaking memory. Before making them long running processes you should get to grips with that.

If you have not a good idea of the memory usage per request and from request to request adding memory is not a real solution. It might help for now and break again next week.

I would keep running separate processes till memory management is under control. If you have response problems currently your best bet is add another server to spread load.

The very first thing you should be checking is whether the clients are actually using the keepalive functioality at all. I'm not sure what you mean by an 'API server' but if its some sort of webservice then (IME) its rather difficult to implement well behaved clients using keepalives.(See %k directive for mod_log_config).

ALso, we really need to know what your objectives and constraints are? Performance / capacity / low cost?

Is this running over HTTP or HTTPS - there's a big difference in latency.

I'd have said that a keeplive time of 10 seconds is ridiculously high - not low at all.

Even if you've got 90 clients holding connections open, 4Gb seems a rather large amount of memory for them to be using - I'e run systems with 150-200 concurrent connections to complex PHP scripts using approx 0.5Gb over resting usage. Your figures of 250 + 90 x 20M only gives you a footprint of about 2Gb (I know is not that simple - but its not much more complicated).

For the figures you've given I wouldn't expect any benefit - but a significantly bigger memory footprint - using anything over 5 seconds for the keepalive. You could probably use a keepalive time of 2 seconds without any significant loss of throughput, But there's no substitute for measuring the effectiveness of various configs - and analysing the data to find the optimal config.

Certainly if you find that your clients are able to take advantage of keepalives and get a measurable benefit from doing so then you need to find the best way of accomodating that. Using a threaded server might help a little with memory usage, but you'll probably find a lot more benefit in running a reverse proxy in front of the webserver - particularly which SSL.

Besides that you may get significant benefits through normal tuning - code profiling, output compression etc.

Instead of managing the KeepAlive settings, which clearly have no real advantage in your particular situation between the 3 options, you should consider switching the Apache to an event or a thread based MPM where you could easily use KeepAlive On and set the Timeout value high.

I would go as far as also considering the switch to Apache on Windows. The benefit here is that it's MPM is completely thread based and takes advantage of Windows preference for threads over processes. You can easily do 512 threads with KeepAlive On and Timeout of 3-10 seconds on 1-2GB of RAM.

WampDeveloper Pro - Xampp - WampServer

Otherwise, your only other options are to switch MPM from Prefork to Worker... http://httpd.apache.org/docs/2.2/mod/worker.html

Or to Event (which also got better with Apache 2.4)... http://httpd.apache.org/docs/2.2/mod/event.html