Intro on caching & datastore
 

Anyone kind enough to write a quick intro on template caching and datastore? Basically:

• If I create a new template, how do make sure it gets cached, and how do I call it from the cache?
• How does vB know when the cache needs to be updated? Especially since the templates usually depend on the user's variables?
• What exactly does the datastore do?

By putting it in the $globaltemplates array, you don't need to call it from cache.
Templates dont really get cached. They are just already read from database all at the same time in a single query when the script starts. If you use an 'uncached' (ie not read from database on script start) template, then for each template an additional query is needed when the template os first used.
Store data :D The datastore is mostly used to store a serialized copy of the data from amy rows into a single datastore row.

Got it - so the template "cache" is not really a cache, but an aggregator, on the queries.

I seem to get slowed performance the first time I load a page after modifying it's template - but I guess that must be do to MySQL or OS caching, not vB then, yes?

Too bad there is no "real" caching done, then. I would guess that 90% of the html could go into a cache (ie, is not personalized), and that a cache could get up to a 50% hit rate.

Think about it: Cache the html for forumbit, threadbit, and postbit - everyone's looking at the recent ones - you're talking a major speed up.

Templates are already preparsed and stored like that.

I was referring to storing the actual rendering of the particular bit, not the generic template.

Example: This thread so far has 4 post bits. They could be cached, with full html (provided we don't mind if the post count under each user gets a bit old) - major performance increase!

That would be extreme difficult to do i guess, for a few reasons:
- It is dynamic content
- Content can be different depending on the viewer (permissions, buddies, postdate/time/timezone,....)
- on a busy forum with a lot of posts, the cache would get so big that searching the cache would take so much time that it has a reverse effect.
And probably many more reasons.

How would one place data into the datastore and pull it back out. For example if you wanted to do something easy like sum up all a forums views and output on the forumhome page and use the datastore to avoid querying on each page load?