I wrote a little thing about Tag Caching... hope its' correct and helpful :slightly*smiling*face: ht

Love it! Also.. not sure I’ve mentioned it yet.. but love to new site.

Cheers @tomjaeger

Great post.

For your use case I’d also use cache_prefix="global" because you want to grant permission site wide.

The cache<em>prefix is something I haven’t explored yet. When you use a specific cache</em>prefix what are the avenues for cache invalidation?

I use tag cache heavily with a refresh value of 1440.

There aren’t any cache clearing controls. EE clears the tag cache liberally and frequently as you update content, and clears the whole cache.

You could build something that erases certain cache directories for certain reasons.

Sorry, I should mean — there aren’t any tag-based, partial-cache-clearing controls. There is a page in the CP that lets you clear all tags. Or you can update a template, entry, channel, field, category, etc. etc. etc.

I guess I don’t understand the advantage of using a cache_prefix if there’s no way to granularly invalidate cache.

Maybe the ecosystem is missing a plugin that can read and clear all of EE’s various cache types.

The advantage is, you can cache a tag once and have that affect every page’s performance — or even a sub-set — rather than having to cache the tag on EACH page it appears. It makes filling the cache faster and more efficient.

Im loving this thread!

Okay, that is good insight @hopstudios

I could talk about cache all day

Here’s a hypothetical….

Say I have a blog landing/archive page containing a blog entries loop: {exp:channel:entries channel="blog" limit="8" dynamic="no" paginate="bottom" cache="yes" refresh="1440" } .... It requires pagination. What is the most efficient way to cache this?

Would it be something like cache*prefix="blog"?

Say I also have category landings/archives, would I use a different cache*prefix for each category?

Maybe this a bad example because it falls into a different use case.

Does using a cache_prefix break the pagination?