rawalex

iridiax, the server is dedicated, and otherwise extremely fast. The blogs only ping the usual suspects. Removing 25% of the old posts from the blog suddenly made posting faster. The only plugin in use (outside of askimet) is the google sitemap, which is the latest version and takes about 15 seconds to run.

Seems to be issues with poor indexing and way too much stuff being done during what should be a simple posting process.

I would suggest that you perhaps have way to many plugins in general. You might want to go through your list and see what ones you really need.

google sitemaps, I have the latest version (updated 2 days ago, I think), which is slow but not the source of the issue.

that memory error actually appears to be an “end of physical and swap memory”, which may mean that your server was very busy at the time.

arnee, one issue I think is that you are running part of the sitemap build against items in the wp_post file that isn’t indexed, so it is taking an incredibly long time to do the job. I have one blog with 11,000 posts that takes more than 90 seconds to build, which is 5 – 8 times longer that a blog with half that many posts, so it shows a failure to scale. You might want to reconsider your methods for obtaining the data and sorting it, making sure that you are querying in the most effective way, and perhaps asking the wordpress people if they would be nice enough to add an index to make this easier.

At this point, I have had to put a hard cap on the number of pages in the sitemap, just to avoid failures and using up significant amounts of server resources.

No, minimal plugins, nothing in the posting area (no tagging or other). This is a very clean and basic blog, just has a TON of posts.

As a test, I duped the DB and removed about 25% of the posts. The adding of a new post was much faster. That tells me that some of the code in there is doing something the wrong way, because it doesn’t scale right.

Bumping this up to the top. I can’t understand why the simple concept of adding a post should run a (pretty powerful dedicated) server into the ground.

I have found plenty of things that are checked and rechecked that aren’t indexed… like wp_post post_parent.

HELP! 2.5.x has turned into a major slowdown in life.

The Visual editors does a terrible job with imported text, because it re-encodes it for UTF-8 before writing it to the database. This step often breaks coded entries, especially if you have a missing tag or a leading space or some other issue.

Hopefully the update of 2.5 will fix this rather major annoyance.

One more bump to see if anyone has a clue on this one, before I make a trouble ticket out of it.

I would check to see if you are getting hit by comment spammers or others. If you have access to stats on that host, see if there are a ton of requests for xmlrpc or similar. You can also check for everything from hot linking to your RSS feed being used “live” on someone else’s blog (pulled for every visitor they get).

Check things too like slow mysql activity, slow queries, etc.

Anyone?

Keith, bad news for you: the guys doing this sort of thing use proxies and servers located in the US to cause the infection – the destination of the traffic is china (and then actually Russia… but that a longer story). So you can end up with these things all over your blog even if you have all of the eastern block and communist world blocked.

If you are going to log queries, I would suggest only logging update and insert queries, to keep your log a little shorter. Otherwise you will end up with a huge log and it will be difficult to spot anything.

Otto42, I have seen how this is done,and it is pretty simple actually. The content appears to be changed during an edit started via xml-rpc. They are pulling the post, adding the code, and re-uploading the post back into place with the new code, all while NOT actually triggering an edit or update.

There is no indication of direct connection to the database, which would be impossible anyway because my DBs are locked down and restricted to localhost access only. Thus the only way the can make the change is by executing code on the server.

I have seen this on multiple blogs, each of which has different user and password combinations.

This is a major issue. When google sees this on your pages, your blog goes immediately into their VERY bad last for linking to a bad neighborhood, for installing trojans, and as such, you lose pretty much all your traffic in very short order.

It’s a hacker abusing wordpress to install viruses and toolbars onto your visitor’s computers. Check all the posts in your database, the code is added to your actual posts.

I got it in 2.3.1 for sure.

This is an XML-RPC style injection – this little bugger has hit a whole bunch of my blogs. I noticed one today on a site I am sure I checked 2 days ago, with 2.3.2 installed.