WordPress-breaks through the performance bottleneck and uses the WordPress site group for Seo promotion

WordPress has low concurrency. On a Linux machine with a dual-core 2.5G + and 2g memory. Use the AB command of Apache to test it. Concurrency is about 6 to 10. This speed is a joke for the SEO strategy of the website group. Deploying 50 WP blogs on one server is basically the limit. Once Google comes, it will basically be inaccessible to the blog. In many cases, a database connection error will be reported. This is disastrous for Google spider. (The Website access speed is also ranked by the website ).

Is there any way to increase the number of WP blogs installed on a single server, and maintain a good access speed when Google comes?

This article will discuss how to deploy more than 100 WordPress blogs on a server (to open a blog normally when Google spider or has a large access volume)

Problems to be Solved

* Maximum number of connections to the database

WP is hard to hurt by MySQL. In mysql5.1 + and later versions, the default maximum number of connections is 151, and the previous version is 100. This concurrency is not enough for servers with 50 blogs. Since Google spider, there have basically been some blogs with database connection failures.

I usually Modify/etc/My. in the CNF file, the maximum number of connections to MySQL is modified to 1000. In fact, this value is too large and it is not good. The number of valid connections that can be opened on Linux servers and Apache is not very large under the memory limit. More than 300 are dangerous. If it is 1000, I think you cannot log on to SSH either. You can only quit ~~~

OK. Modifying the maximum number of connections of a database is only the first and simplest step. In fact, this modification cannot be changed. We only need to solve the expected problems of MySQL. The following describes how to optimize WP.

* WP blogArticleStatic

Run the AB command to enable the WP super cache plug-in. The concurrency of the same server is about 1300 +. This is quite different from concurrency 10.

(For details about how to install WP super cache, refer to other materials.Or I will add an article next time.)

What I want to talk about here is:

After WP super cache is installed, you must first enable preprocessing of all article pages (create cache files that never expire)

Create a robots.txt file for each guest, and block the crawling of tags/, category/, 2012/, and other URLs.

Add a Google sitemap tool for each blog to generate a site map.

For newly added articles, the cache system must generate a static cache file after one access. For a promotion blog, a webmaster usually has hundreds of blogs in his/her hands, and posts blogs are usually automatically published using pseudo-original software. A blog may post dozens of articles every day. It is impossible for a blog to post articles and click on the pages one by one (so that WP can cache static files ). So here we needProgramAfter publishing an article, simulate a spider to pick it up. In this way, when the spider collects the data, Wp has prepared a static page for it, instantly increasing the access speed to the WP blog by several levels ). However, some of the Blogs Google are very fast and may have published an article five minutes later. Therefore, the best strategy is that after an article is published, the program can access the currently published article, so that even if the spider collects the article within five minutes, our Wp has also cached the corresponding static files.

 

 

Pay attention to the configuration of WP blogs for promotion.

*For example, the robots.txt file is used to block tag, classification, and archive capturing.

User-Agent :*
Disallow:/WP-
Disallow:/feed/
Disallow:/comments/feed
Disallow:/trackback/
Disallow:/sample-page/
Disallow:/Hello-World/
Disallow:/category/
Disallow:/Tag/
Disallow :/2012/
 

*Disable blog post comments

*Users who need to log on to comment on the article can

*Cancel pingback and so on

* Cancel publishing the URL in the article Ping (this is critical. If you use the WP blog for promotion, the URL of the website to be promoted will inevitably appear in the article, if this option is not disabled, after publishing an article, WP will ping the URL in the article. If many blogs on your server are using programs to automatically publish articles, it may be for the promoted server. In the short term, the number of connections is soaring, which seriously results in the failure to access the promoted server)