Yep. Wordpress will eat your server if you don't configure page caching.
At $CORP, the web application went down when some heavy Wordpress traffic slowed down the shared DB :/
At $CORP, the web application went down when some heavy Wordpress traffic slowed down the shared DB :/
It's not optized at all.
At the time I was tasked with evaluating it as a "cheaper" replacement for an expensive, managed CMS. My conclusion was it would end up being more expensive to accommodate all of this inefficiency with caching galore not to mention support and dealing with a loss of dynamic web sites.
I looked again last year, assuming it had greatly improved, had replaced all that with GRPC or graphql and nope, still horrendously designed.
I wonder if it's intentional or just a case of support for backwards compatibly.
Now, don't get me wrong, I use and like Wordpress. There is not more versatile yet approachable blog/CMS/whatever out there, the ecosystem is huge and it's my go to tool when I want a quick and dirty solution.
But it doesn't change the fact it has been badly designed from the start.
Popularity in software doesn't reward good design. It rewards solving problems.