Can wordpress handle 10,000,000 blog posts?

Statics are more easy and performant - but storrage will become an issue there, at one point.
And you can run in "Too many open files" Server Errors.
Been there allready =D
These problems are easier to fix with server admins on VPS or with dedicated server
Than fixing mysql in wodpress :D
You can also go with cloudflare, even premium
 
Than fixing mysql in wodpress :D
Obvious ;)
My road, where I basicly have been falling forward was:
1. Wordpress
2. Statics
3. Statics with NGINX variables
3. PHP with MongoDB
4. PHP Frontend with MongoDB & FastAPI as backend
Let's see, what to come, when everything crashes again, like a professional xD
 
Obvious ;)
My road, where I basicly have been falling forward was:
1. Wordpress
2. Statics
3. Statics with NGINX variables
3. PHP with MongoDB
4. PHP Frontend with MongoDB & FastAPI as backend
Let's see, what to come, when everything crashes again, like a professional xD
Do Python + Django, it's done for massive scale
 
Do Python + Django, it's done for massive scale
Yeah, thought about that one as well, but had to change fast and fastAPI is a more straight forward python solution - And I still have to do some Frontend performant work, working with spintaxes of every textpart - PHP 8 is just a small amount faster and I'm more used to it, than Django^^
The Frontend can be scaled easily (with load-balancing and stuff like this) anyway, with the hidden API based backend.
 
Yes. WP loop queries have no inherent technical limitations.

However, there is always a limit to the number of resources (CPU and memory) allocated to specific servers and configurations.

For example, WordPress is like your mobile operating system. If you have a high config mobile, you can use unlimited applications. Suppose you have average config mobile, then using many apps will slow down your phone. So same as like this

WordPress is a good choice for blogging, but you have to note two things before creating an unlimited post.

Image:
This is an issue if you use images in your posts. considering the default thumbnail sizes of every image (thumbnail, medium, large + the image itself), you will end up having at least 4 generated images for each post (assuming each post only has 1 image). This means you will end up having 10,000,000 images.

Database:
WordPress creates entries other than the original post itself in the database. Each post can have unlimited meta attached to it, limited by the database itself. A complicated meta query will take considerable time and resources if your posts have a lot of metadata (Images, Custom fields, etc).
 
Wordpress doesn't have any limit on the number of blog posts.
limit on the space of uploaded content.
 
Yes it can be used for that amount of posts, but please note that you need a solid VPS or dedicated server with optimized caching modules and mariaDB.
 
It can but the real question is should you? At that scale if you're putting any real effort and if you have sizeable investment you should probably create your own cms or use something like ghost.
 
if your server is setup for wordpress, it can handle that and more.

use mariadb instead of mysql for faster database resolve, and use nginx for faster requests & caching.
 
To what number of posts / pages?
Per Domain random, between 200k to 500k with 50k Domains at high point, so about 15,000,000,000 Pages, regenerating a bunch of em every day.
Was a crazy setup, with something like 9 good VPS Webserverr for the Statics alone, one strong dedicated for rendering this stuff and 1 for routing the traffic^^
 
I have a question, what if there are no hosted images, no hosted videos, no custom fields on server just a little text and links, would it be easier to handle that much posts?
 
400k pages with Node, NextJs and Mongo.

To be honest, with WP it depends how much you will stress out mysql.
 
I have a question, what if there are no hosted images, no hosted videos, no custom fields on server just a little text and links, would it be easier to handle that much posts?
Basicly yes. Of course. When you think about mysql, every meta data you need for a post is basicly a more complex querry, or think of it, like an extra request, to the db.
You mostly come to some douzends "requests" to the db anyway, because WP has to ask the DB for some shit like configs and stuff like this - it has to render every single page with the related informations in the DB.
So, if you reduce the requests, like by not using custom fields and stuff like this, your DB will perform better.

But thats a bit oversimplified as well - search querries and in particular random querries are very intensive again.

Your DB will be the very first bottle neck...
At 10 mio pages on a medium class server, this might work. I made a setup some years ago, stretching to 2mio Woocommerce Articles, wich have even more mess in their meta, with some DB tweaking, this can work. At least at medium load - a problem that might happen to you, is that the search engine bots will basicly ddos you.

What you can do as well, is just sourcing out your posts to backend server, that will serve you the content as json for example and then working with parameters, so that WP isn't even working, just requesting the article for example by the Get parameter given.
So you would be able, to integrate stuff into your existing WP.
 
Yes it can handle this many posts if you have the right hosting.
 
Lol what matter is your server. as long your server can handle it no problem than
 
Back
Top