[TECK]

Originally Posted by djohn

Right, I've updated, but I can't figure out what template is uncashed, there's a 1 next to all of them. See screenshot.

The number in parenthesis (1), for example, indicates how many times the template is called by the script. This is just a reference for your code. Look at the "forumhome_forumbit_levelX".. I bet you have 3 categories and 9 forums (with 2 sub-forums) displayed on your front page... and there are only 2 forums where you got replies.

As Christine mentioned, the uncached template is highlighted in blue.

The "board_incative_warning" template is not cached for server performace matter, and is not something the VB devs forgot.
Let me explain the way it works with the memory server cache so you understand a little better the process.

VB software uses/creates a cache, like a sort of temp folder where is stored important information that is used several times, same like in Windows.
All this information is stored temporarily in the VB database (that is also sanitized on a regular basis by the VB software), so it eliminates the need to scan the tables several times for the same information resulting an increase of the server load.
For example, on the forum frontpage, if you open it for the first time, there will be far more queries performed instantly (14 instead of 8), then when you visit it for the second time, due to the cache process, all temporary information is stored in the "temp" database.

Now, why all templates are NOT cached? The VB devs created a balance between the software and server. In other words, they used this aproach:
If an information is used less then 95% of the cases, there is no need to store it in the server memory/database, because most likely is not very often used, like your "board closed" template. They prefered to trade it for a query, instead of loading it into a temp process, when you use it only once every 500 cases...

That's why you will notice some uncached templates sometimes.

I hope this information helped you to understand better the cache process.