How do you get back to it? Have you had a 30+ days absence from coding? I mean, completely, not even looked at it... what steps did you take to get back to it? I'm surprised how out of touch I am with things...
Maybe I'm gradually losing the remaining of my mind?
I usually take about 3 weeks off around christmas, 30+ has been quite a while... Anyway just pick an easy and/or enjoyable task to start. You haven't forgotten anything, it is just a bit burried :)
"Wordpress becomes inefficient at handling the number of posts somewhere past the range of 1500 to 2500 posts, 5000 to 6000 comments, and about 7000 tags, roughly." -- Hostgator Level 2 support.
I actually thinking about opening a question on WPSE about sites with thousands of posts etc. It's been on my mind since our own platform has grown rapidly...
.... wordpress is never inefficient, it is what you are trying to do with it. 7000 posts in archive with all visitors on home page should never be a problem
@ChristineCooper, obviously the bigger you are the better server infrastructure you need, but this is true for all platforms
True, but with bigger, do you mean bigger DB, or bigger traffic that calls the DB. So if my DB is huge but the same amount of traffic is on the site, then will performance be bad... if you get my point. Because it shouldn't unless if I run some mental queries...
bigger DB is not a problem if you don't need to query often. This is basically about how good can you cache things and how many requests end up being served to the DB. The size of the DB itself is less relevant if you can avoid accessing it
big sites are all about caching strategy. The main thing that just don't work in WP is when you have many pages as the admin for that is just broken
WP doesn't scale well for large amounts of posts because MySQL doesn't scale well for pagination. getting posts 1 to 10 is trivial. getting posts 1 000 001 to 1 000 010 is a nightmare.
depends of course. from my work with sitemaps problems start upwards of a half million posts. but obviously running 100k on shared host might be worse than running 500k on dedicated server.
WP admin causes huge CPU spikes on multiple sites for me. I've noticed an increase of server performance (less CPU bogging after switching to multisite instead of several standalone installs). There were other changes in this process as well. One hosting account, one database, one set of wordpress files, 1 virtual host with aliases instead of multiple virtual hosts, etc. So I'm not sure if multisite in itself made the difference, but overall, my server bogs a lot less now.
I manage the entire setup myself, so I don't have to worry about security risks of using multisite quite as much as those who allow outsider access.
but still the point remains WP Admin uses a ton of CPU on my server. Still... Even after all those changes. Not sure why. Haven't really investigated that deeply.
I've also made some changes to help reduce that bogging by implementing a separate server exclusively for the backend of WordPress. Using HAProxy to route the connections appropriately.
