Laibcoms wrote:

The way I understand it right now is this:
blog-cache - will cache anything that is not originating from "skins"

Uhm, no. The blog-specific cache caches everything that comes from a skin. The global cache caches anything that doesn't come from a skin; for example, the blog templates which come shipped with b2evo use the global cache (these files are all located in the blogs/ folder):

• summary.php

• default.php

• a_noskin.php

• multiblogs.php

[/list:u]

1) Which one is good as a buffer against the digg-effect?

Most of the time I think that would be the blog-specific cache.

2) Which one eats more CPU vs. server RAM?

The caches work identically (it's a class named "PageCache") and store the cached pages on disk, not in the RAM. I don't think the caches affect the CPU much.

3) Good for shared hosting? (low-cost, medium cost, ??? )

Should work anywhere (if PHP can write files somewhere). Well, perhaps you need a little bit of free disk space, but that depends of your average page size etc.

4) How about scripts that are not or should not be cached, are these affected/get cached? (like Analytics and scripts for AdManagers, especially ad banners)

The cache stores the HTML that is sent to the browser, so if you just include a JavaScript using the src attribute of the <script> tag, it will work with the cache.

5) How long does the caches remain? For example the skin was updated, or a part of it (like the external CSS files)?? A publisher can't possibly expect his visitors to "force-refresh" (CTRL+F5)....

Currently for 5 minutes.

Wow, yer a mine of useless information! ;)

¥

Cool. Thanks for the explanation!! ^_^