Wordpress.com serves 70k requests/second using Nginx
highscalability.com
Wordpress.com serves 70k requests/second using Nginx
1–10 of 97 posts
Re: Wordpress.com serves 70k requests/second using Nginx
#2Those must be cached pages from dozens of servers on the backend.
There is no way in heck it's realtime queries.
I can tell when authors are in the WP backend on the server just by looking at the server load because it's crippling.
The wordpress bottleneck is not nginx vs apache vs whatever, it's the problem of loading hundreds of files for any kind of page render (even to just authenticate for ajax, etc.) and over a hundred db queries in many cases.
A cache-miss in WP is a terrible, terrible thing.
Re: Wordpress.com serves 70k requests/second using Nginx
#3Those must be cached pages from dozens of servers on the backend. There is no way in heck it's realtime queries. I can tell when authors are in the WP backend on the server just by looking at the server load because it's crippling. The wordpress bottleneck is not nginx vs apache vs whatever, it's the problem of loading hundreds of files for any kind of page render (even to just authenticate for ajax, etc.) and over a…
Don't forget the version of Wordpress that you download is very different from the version that's on Wordpress.com
Re: Wordpress.com serves 70k requests/second using Nginx
#4Those must be cached pages from dozens of servers on the backend. There is no way in heck it's realtime queries. I can tell when authors are in the WP backend on the server just by looking at the server load because it's crippling. The wordpress bottleneck is not nginx vs apache vs whatever, it's the problem of loading hundreds of files for any kind of page render (even to just authenticate for ajax, etc.) and over a…
Don't forget the version of Wordpress that you download is very different from the version that's on Wordpress.com
I know they replace the database class on wp.com to support replication (I think they even released the code once) but I don't think they do extensive changes otherwise unless you've actually read otherwise.
Re: Wordpress.com serves 70k requests/second using Nginx
#5Those must be cached pages from dozens of servers on the backend. There is no way in heck it's realtime queries. I can tell when authors are in the WP backend on the server just by looking at the server load because it's crippling. The wordpress bottleneck is not nginx vs apache vs whatever, it's the problem of loading hundreds of files for any kind of page render (even to just authenticate for ajax, etc.) and over a…
Don't forget the version of Wordpress that you download is very different from the version that's on Wordpress.com
It's actually not that different, and of course they make as much use of caching as possible.
So does my self-hosted wp blog, for that matter. If you are using WP Super Cache correctly, you can deal with significant amounts of traffic. I've seen peaks of hundreds of simultaneous users on my blog, with a server load < 1. The server is a modest aws small instance.
Re: Wordpress.com serves 70k requests/second using Nginx
#6And how many requests/sec per CPU?
They have like 300 servers and who knows how many cores.
What kind title is this? The target High Scalability reader must be presumed to be a complete fool.
Re: Wordpress.com serves 70k requests/second using Nginx
#7Earlier quoted context omitted.
Don't forget the version of Wordpress that you download is very different from the version that's on Wordpress.com
It's actually not that different, and of course they make as much use of caching as possible. So does my self-hosted wp blog, for that matter. If you are using WP Super Cache correctly, you can deal with significant amounts of traffic. I've seen peaks of hundreds of simultaneous users on my blog, with a server load < 1. The server is a modest aws small instance.
Single author mini-blogs without logged in users are super easy to cache.
But multi-author blogs with thousands of logged in users is a nightmare with wp.
I suspect 90%+ of wp blogs are in the mini-blog category though.
Re: Wordpress.com serves 70k requests/second using Nginx
#8Those must be cached pages from dozens of servers on the backend. There is no way in heck it's realtime queries. I can tell when authors are in the WP backend on the server just by looking at the server load because it's crippling. The wordpress bottleneck is not nginx vs apache vs whatever, it's the problem of loading hundreds of files for any kind of page render (even to just authenticate for ajax, etc.) and over a…
Cached or uncached is not relevant to the article.
They are talking about using nginx as a load balancer. It just proxies all requests off to the application servers that actually prepare the results. This article is really just about the fact that nginx can efficiently service a very impressive number of connections at once.
Those backend servers will be using caches of course though.
Re: Wordpress.com serves 70k requests/second using Nginx
#9And how many requests/sec per CPU? They have like 300 servers and who knows how many cores. What kind title is this? The target High Scalability reader must be presumed to be a complete fool.
According to the article they have 2 thousand servers. These are Dual Xeon 5620 4 core CPUs with hyper-threading.
So that averages out to: 70000 / (4 * 2000) = 8.75 requests per second per CPU.
That seems like quite a low number, I would presume that the load would be shared amongst less servers than this and the others would be used for replication/redundancy.
Re: Wordpress.com serves 70k requests/second using Nginx
#10Earlier quoted context omitted.
It's actually not that different, and of course they make as much use of caching as possible. So does my self-hosted wp blog, for that matter. If you are using WP Super Cache correctly, you can deal with significant amounts of traffic. I've seen peaks of hundreds of simultaneous users on my blog, with a server load < 1. The server is a modest aws small instance.
Single author mini-blogs without logged in users are super easy to cache. But multi-author blogs with thousands of logged in users is a nightmare with wp. I suspect 90%+ of wp blogs are in the mini-blog category though.
Why would multiple authors make a difference?