If it's not really necessary, do not enable caching plug-ins

Intermediary transaction http://www.aliyun.com/zixun/aggregation/6858.html ">seo diagnose Taobao guest cloud host technology Hall

How to say, when preparing to write this article, the mood is a bit heavy--this article has overturned some of my consistent ideas, such as the knowledge of WP cache plug-ins.

I originally thought, open cache plug-ins, such as WP Super cache, Cos-html-cache, W3-total-cache, etc., you can save a certain amount of system resources, and speed up the speed of the network display (for the server in the United States, I, speed is very important), So in the beginning of the blog has not very large flow of time to enable the cache plug-in, use has been nothing until I recently used a host.

In order to better learn WP, I set up a new host on a WP, and installed a number of commonly used plug-ins, a full 15 + (WP Super Cache in which, but not enabled), but the host after the activation of these plug-ins are often suspended.

I am very confused, so contact the host to inquire what is going on, the answer is: The Web site consumes the amount of memory outside the allowable, occupy too much resources, when the resources occupy more than a certain limit, the account is suspended.

I took a closer look at the limitations of the host for resources, and found that the maximum memory limit is 32M, which must be too little. I thought of it. Enable caching plug-ins to reduce the program's footprint on resources.

But it backfired, after the WP Super Cache has been enabled, the number of accounts has been suspended more, I am very puzzled.

Thinking about it, or decided to deactivate some of the plug-ins are not necessary, but the excessive resource consumption caused the problem of the account suspension is not a fundamental relief, or often happen, which I was thinking.

I think, will not be the cache plug-ins caused by the problem?

Because WP Super Cache is only a semi static plug-in, it is often necessary to generate a certain amount of HTML files, while the generation of HTML files is a very resource-intensive operation, in the resource constraints are not very strict host on this is not obvious, but in my memory usage of only 32M mainframe, Creating HTML is still a bit of a struggle.

So deactivate WP Super Cache, the problem is really greatly improved, almost no recurrence of the account was suspended.

I have come to the conclusion that

The 1,WP cache plug-in is useful, but it needs to be the case;

2, only when it is really necessary to enable caching plug-ins;

3, try to enable completely static, such as Cos-html-cache, rather than semi static plug-ins;

4, if the host is really unable to support the site, or the early replacement of the host is wonderful.

Original articles such as reprint, please specify: Transferred from the Nazi blog, http://nacv.info/.