Our host has brought us down a few times now saying we're killing the server. The finger he pointed was at sitewide tags, saying every hit on the front page causes hundreds of db queries.
He have a lot of tags on our pages and yeah it would seem that there might be a lot of db touches involved if the code is not yet optimized. I noticed that by default the limit for sitewide tags is 5000.
I was looking to solve the problem by limiting the number of tags displayed per story page to 10 of them at random. I've looked around but cannot find where to adjust the database call. Any help out there?
And if you ant to display less tags, use a different tag cloud widget. Plenty in the repo.
Also, if you are on shared, might as well start looking for a better host, becasue as your site grows you just need more resources.
andrea wouldn't that depend on traffic? I don't want server resource requirements to grow with the size of the site but with the demand created by traffic. The former is not sustainable for us. The latter definitely is.
It seems like some plugins simply aren't scalable at all while others (the hosts recommend using no plugins) are.
Or are you saying MU itself has gross scalability issues?
Oh, mu can be scaled just fine. As you're finding, some don't scale well (tho I hadn't seen any issues with SWT). And yes, the size of the site will use resources too.
Tho I'd like to see where their "hundreds of queries" came from. Got a link to your site?
smazsyr
Member
Posted 14 years ago #
I understand that if Sitewide tags posts more than (by default) 5,000 posts to a group blog for showing child posts on a network, it will begin deleting from oldest first.
What if the plugin is set to post to the main blog? Please tell me (please oh please oh please) that it doesn't begin deleting posts from that blog.
If not, is it just that that function is ignored when the main blog is the target?
yes, it does delete regardless. But only from the tags blog, not the original blog.
And you can set that number to a million if you like.
smazsyr
Member
Posted 14 years ago #
I'm sorry for being dense.
I have Tags Blog enabled, and a post archive at bloggers.MainBlog.com
I also have the 'Post to main blog' option enabled, to get child posts on my main homepage.
What you are saying is that posts in bloggers.MainBlog.com will be deleted as needed, not those from MainBlog.com, correct?
I also have the 'Post to main blog' option enabled, to get child posts on my main homepage.
If you have this option checked, then you will only have new posts going to the main blog.
Not bloggers.MainBlog.com. It does not send to both places, it's either/or.
When I say :"tags blog" I mean whatever blog you've set to push the posts to. If you've set it to the main blog, then I mean the main blog.
smazsyr
Member
Posted 14 years ago #
OK, thank you. That is not clear in the text supplied with the plugin (at least to a guy like me.) Also, I htink that's pretty dangerous, allowing the plugin to delete old posts from the main blog -- unless it knows how to delete only those posts that it itself created, and sticks with those.
