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.

Thanks Teck.
I just removed Erwins' stats and installed yours... much more info :D

[high]* BarBeQue clicks install[/high]

still getting an error on that line

It is your board_inactive_warning -- note the blue highlighting on it.

:):

I was just about to say that. :)

I noticed that without the update installed, only cause i had the board inactive, and when the board is active i have no uncached templates.

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. :)

Chuan, what portal you use?
Is extremly intense on the table scans... Holly molly...
The number of queries is ok, but the code is not very strong, IMO.
Compare it yourself with any forums page. As soon as you go over 20% MySQL, you got to ask yourself what bad code you added there to perform table scans that generate those results...

Teck -- So you know, the blue highlighting isn't working in Opera 7.23. It is fine in IE 6 and FireFox 0.8.

Just in case you get any questions from folks who aren't seeing which template is the issue -- it may be their browser.

:)

it looks like the vBindex portal, but he has no copywrite info at the bottom, so i dont know.

as for the vBindex portal, this is what i get on portal home,

Page generated in 6.73733711 seconds (5.21% PHP - 94.79% MySQL) with 17 queries
NO Uncached Templates | DEBUG Mode OFF | GZIP ON (level 1) | 0.31 : 0.13 : 0.09

The slow loadtime is only because of the weather block i have on the portal home.

if I remove it.

Page generated in 3.35731196 seconds (9.05% PHP - 90.95% MySQL) with 17 queries
NO Uncached Templates | DEBUG Mode OFF | GZIP ON (level 1) | 1.11 : 0.31 : 0.15

is what i get. I'm sure NTLDR's code is fine. :p but I'm no coder, so i wouldn't know. :D

Thank you very much TECK, that did help a great deal. You were, I do have 3 categories and 9 forums with 2 sub-forums :)

Thanks a lot again :)