12,000 Requests per second with Nginx, PHP and Memcached

Re:12,000 Requests per second with Nginx, PHP and Memcached by edanm on Tuesday February 15, 2011 @04:05AM (#2220635)

Thanks, I'll look into those.

When you say ditch Apache, do you mean completely? I know a fairly common setup is to use nginx+Apache to serve Django (with nginx serving the static content and Apache the Django code). Should I be running everything from nginx?

[ Parent | on HN ]

Re:12,000 Requests per second with Nginx, PHP and Memcached by jacques_chester on Tuesday February 15, 2011 @04:09AM (#2220643)

Personally I don't see the point in keeping Apache. It just adds more moving parts and more points of failure to have two HTTP daemons.

I'd ditch it entirely and switch to WSGI or FastCGI.

[ Parent | on HN ]

Re:12,000 Requests per second with Nginx, PHP and Memcached by 2mur on Tuesday February 15, 2011 @11:53AM (#2221980)

You should at least try nginx/gunicorn (http://gunicorn.org/). And if your clients are constantly pinging and the data hasn't changed, make sure you are caching it in memcache (etc) to relieve the database.

http://ericholscher.com/blog/2010/aug/16/lessons-learned-das...

[ Parent | on HN ]

Re:12,000 Requests per second with Nginx, PHP and Memcached by edanm on Tuesday February 15, 2011 @12:04PM (#2222043)

Honestly, I'm a little scared of using something like gunicorn. I could be wrong, but it seems like an extremely new technology, especially when compared to Apache, which has a lot of history behind it.

[ Parent | on HN ]

Re:12,000 Requests per second with Nginx, PHP and Memcached by antihero on Tuesday February 15, 2011 @11:59PM (#2225075)

You can have a failover, so if one breaks you can quickly boot the apache one back up.

[ Parent | on HN ]