Caching Question: Page Caching vs. Snippet Caching

and Jason, how do you decide when to cache or not cache a snippet?

Quote from: ChuckTrukk at Jan 29, 2009, 12:00 AM

and Jason, how do you decide when to cache or not cache a snippet?

By deciding which content can be cached and which content needs to be dynamic every time. If the code is not affected by user, request or other outside variables/data, generally it can be cacheable. If it needs to change based on request variables, user security, or the domain being requested (i.e. if you are pointing multiple domains at a single site), then generally you don’t want to cache those, otherwise, everyone who visits will see what the first person visiting saw (cause it got cached based on his identity or request params, etc.).

simple enough. thanks.

Jason, I’m working on MODx cache method, Is it not funny to have all (any)contents being saved as a cache on a single file?, Still i didn’t digged the Revolution to see how it accomplishes the cache thing, But for some of my projects i see its going to break the 5000 document limit sooner than later so i need to work on a solution that doesn’t get to the dead-end.

Something that splits the cache file into several other file based on contents shared points, say snippets-how many-which, Documents/how many/from what category or kind, and other data/content type...

I’m not sure that i explained the idea very well but seems some of you guys have done something to pass over the 5000 limit, so I’ll be glad if you point me to some tricks or i have to think about the way of implementing such a way described above.

Thanks for any comments :-]

Revo caching model is completely different and handles more than 5000 resources (currently "documents") gracefully.

I like the idea of anything that will help the evo cache.

What would happen if you had a base cache and an individual cache for each page? Im just wondering.

Quote from: ChuckTrukk at Feb 07, 2009, 08:08 AM

I like the idea of anything that will help the evo cache.

What would happen if you had a base cache and an individual cache for each page? Im just wondering.

That’s exactly what we have.

Quote from: MotSmart at Feb 07, 2009, 05:44 AM

Something that splits the cache file into several other file based on contents shared points, say snippets-how many-which, Documents/how many/from what category or kind, and other data/content type...

I’m not sure that i explained the idea very well but seems some of you guys have done something to pass over the 5000 limit, so I’ll be glad if you point me to some tricks or i have to think about the way of implementing such a way described above.

Your first suggestion is called Contexts, and is part of Revolution. As for Evo releases, I do not foresee anything that could solve this other than the things that have already been suggested (moving snippets and plugins to external files included via a single snippet, moving chunks to includes, etc.), but may not be practical unless you are developing all the components of your site from scratch. Otherwise, the only thing that’s going to help is faster machines with more memory and less shared traffic.

Thanks Ryan, Jason, Maybe thats why you named Revo, Revo.. but, For me its not fair to have Evo left aside under 5000 doc limit.

ChukTrukk, Have to do something for Evo cache, ah! takes time! :-]

Quote from: MotSmart at Feb 10, 2009, 05:12 AM

Thanks Ryan, Jason, Maybe thats why you named Revo, Revo.. but, For me its not fair to have Evo left aside under 5000 doc limit.

ChukTrukk, Have to do something for Evo cache, ah! takes time! :-]

IMO, sometimes it’s better to accept that something has evolved as much as it can, and only it’s offspring can effectively continue to progress the ideals that the ancestor began.