[Plugin: WP Super Cache] Fastest setting for Non-Blog use of cache

The issue is for me, is some pages seem to load immediately and some take a long time. It seems pages that are caches already pop right up, and expired pages take 30+ seconds to respond. I would like the pages to never expire?

Are you talking about “pages” or “posts”? If you want posts to never expire, just put the GC to “0”.

Double check at the bottom of the source, of the slow loading pages/posts if the pages/posts are actually cached.

Note that if you set “Clear all cache files when a post/page is published”, indeed, the cache will be flushed. If you do that, then it is good to manually preload (otherwise you will have to wait until the next preload cycle – 60 min in your case), for all pages/posts to be cached again (except those pages/posts that get visited in the mean time).

Donncha to correct me if I am wrong.

Peter

thanks for your response.

I only have 14 “posts” at the moment, and update those rarely.

Mainly we are dealing with the site in the form of “pages”, currently I have 238.

So if I set GC to 0, and preload cycle to 60 minutes, will the cache actually be regenerated every 60 minutes? or only if the cache was cleared? Hopefully only once cleared… so then I would set it to 30?

I would like to assume that the slow pages have been cached, only because it says I have too many cached pages to show content.

It does seem to be faster now… but really depends on the time of day, and not sure if its due to GC. I will set it to 0 now and see how that works.

Thanks Peter

James

“too many cached pages to show content”, is just a notice for the dashboard. The pages are actually cached, but there are too many to show the individual cached pages/posts on the “content” tab.

For as far as I understood, the GC has no influence on the expiration of preloaded pages (Donncha to correct me if I am wrong).

If you set preloading to 60, and have “preload mode” enabled, then all pages/posts will be pre-cached every 60 minutes, so 60 minutes will be your expiration. If in the mean time you would have created new pages, in between preload cycles, the normal cache mechanism would cache the page (if visited), and those would expire with the GC value.

So in your case, you have two options:
– preload to a high value (even more than 60), but manually delete the cache and manually reload when you update a post/page for force the caching.
– preload to a low value, and know that updated pages will be automatically recached at the next cycle (thus no manual work).

If you give me the URL to the site, i can see if the cache is actually working on the different posts/pages.

Peter

I notice that only publishing a brand new page clears the cache.

Changing a draft to published, a published page to a draft, moving a page to the trash, changing a pages name, priority or slug will not clear the cache. Any way to change that?

Thats a redirect to the site… thanks for the help

James,

Nice clean site, well done.

For as far as I can see, your site is running on Godaddy, probably shared hosting. Their speed is pretty uncontrolled (and according to my 3 years experience not worth a penny), so you will immediately see the difference between a cached and a non-cached page. (as you noticed) The non-cached pages were very slow, even though they did not have a lot of data.

A site like yours is – as you described – ideal for pre-loading.

Now maybe you are still working on the site, but I saw that most pages were not cached until I visited them for the first time. After that, they remained cached, and loaded faster on a re-visit.

Do you have the preload on at the moment?

PS: you can always check which pages/posts are cached, by checking the cache files in /wp-content/cache/supercache/yourdomain/*… If you delete your cache, and then preload the cache manually, there should a be folder for every single page or post you have (after the preloading finished)…
I think there is a problem in preloading (if at this very moment you had it all preloaded).. What is the number of posts/pages does the preload tabs shows?

Peter

Peter-

“Currently caching from post 100 to 200.”

“WP-Cache (45.00KB)

* 13 Cached Pages
* 0 Expired Pages

WP-Super-Cache (3.25MB)

* 199 Cached Pages
* 0 Expired Pages”

out of 232 Pages it is mostly cached at the moment.

It is godaddy, trying to keep the cost down… but possibly not worth it. I was hoping I could solve the problem with caching…

James

On a side note… I have noticed that since I have adjusted the settings on the cache… not sure which setting did it, I get the occasional 500 error trying to open the login page for wordpress… and also trying to navigate the administration pages. Reloading then opens it fine.

Godaddy, right? If so, then the 500 error has nothing to do with you. A typical Godaddy error.

HA! Figures. I complained to them about the slow speed issue before adding the WP-Cache… they of course told me they were “unable to recreate the issue” and that “the site is very snappy on our end” and basically blamed my ISP.

Right now I am paying $3.74 per month… hard to beat, what hosting would you recommend I consider?

James,

my take on it: If Godaddy already times out with a 500 error on a single non-cached page load, then imagine what it will do if it has to (pre)load 232 pages every 30 or 60 minutes… It will take a long time. So my bet is that the preloading cycle does not finish regularly, thus you always have a lot of uncached pages.

I am not sure but think that when preloading, Supercache first deletes the previously loaded pages and then the preloading starts. So if preloading is that slow, there is a good chance you will hit a non-cached page.

So the task to do is to watch the progress of the preloading. If you see indeed the preloading going very slow, not finishing in its cycle, then that is the problem you saw to start with “Why am i seeing so many noncached pages”…

On Godaddy, the only thing that could help you a bit, is to go to gridhosting (does not cost you anything, and is done for free, automatic and conversion is done pretty fast). Grid shared hosting is emmm.. less unreliable.

Since I left Godaddy for Hostgator, my life took a turn for the better. (I went pretty far, and went for VPS hosting, so I could control the whole server setup… Night and day difference.)

PS: I still have several test servers on GoDaddy I use to design new blogs. On several of them, with 200 posts content, I have caching running to test things out. I often get an automated email from supercache that the preloading stalled. So there you go.

Peter

$3.74/month… ?? did you read the link I posted? “Share hosting: pay peanuts, get monkeys”, which tells my story with Godaddy. “Can not recreate the issue” is all to familiar to me.

I honestly believe that a slow/erratic site is worse than no site, certainly as in your case, you want it to be business card for your company…

You would not print paper business cards on oily stained ragged paper neither, would you? ;-)))

Yes. I did review the link, and I am debating that issue right now. I do want a reliable host indeed, but the jump up in expense is a big one… so I need to consider all options. I was hoping I could deal with most of my complaints via the WP-Cache… so I will allow that a few days to better gauge its performance. I tried setting the preload to 30 minutes, and it seems it doesnt reload anything since nothing has changed. Does that seem like what you would expect? It was what I hoped…. before that I thinking of setting it to 1440 or 2880 just to limit the rebuilds.

—-
I take that back, just logged back in and it is rebuilding the entire cache… oh well. i guess I will go for 1440.

For some reason I don’t receive any emails during this process, no matter what setting I have, and I have tried a few different addresses, and nothing in my spam filter.

Also check if you are on gridhosting. As said, does not cost you anything, and the performance is slightly more stable.

If none of that works, and you can not move from Godaddy, then the only thing to do involves manual work:
– put the preload to 0 after a full preload cycle.
– put the expiration time to 0
– if you modify a page, manually delete that page from the cache files directory
– when not logged onto WP, go to to that page, so the cache is generated.

but that is all pretty far fetched.

Peter