Version: 1.00, by Erwin
Developer Last Online: May 2013
Version: 3.0.3
Rating:
Released: 01-04-2004
Last Update: Never
Installs: 190
No support by the author.
Version 1.0 - works for most servers Updated 1.1 - optimized code Updated 1.2 - added names of uncached templates!
Okay, the original was by TECK. This is NOT based on his code - it is based on vB3's native code. If TECK wants me to remove this, I will do so. This is just my version that I use for my private forums.
Information shown: 1) Page loading times 2) Number of Queries 3) Server Loads 4) Number of Any Uncached Templates 5) Name of Uncached Templates (NEW!)
By default only an Admin (usergroup 6) can see it. Feel free to modify this bit.
d3nnis:
Do you have access to server's shell? If so, what's output of "ls -l /proc/loadavg" and
"ls -ld /proc" ?
Anyway, you might want to revert to previous version of the hack for the time being...
d3nnis:
Do you have access to server's shell? If so, what's output of "ls -l /proc/loadavg" and
"ls -ld /proc" ?
Anyway, you might want to revert to previous version of the hack for the time being...
the server is owned by me. I will check it out tonite when i am back home.
To cache a template, you need to find out which ones are not being cached. Then you add it to the top of the PHP file being run, in the section where it lists templates to be cached.
I may add a feature to this hack so that uncached templates show up with names.
that will be great!
by the way what kind of problem does uncached templates gives? increase server load?
by the way what kind of problem does uncached templates gives? increase server load?
Each vb3 page is getting all "cached" templates in a batch, in one SQL query. Every uncached template needs separate query to run, thus increasing load on SQL server.
To find out what templates are uncached, one have to run the script in debug mode. Of course tt could be done simply by putting $debug=1; at the beginning of the script, but you don't want to scare your users, do you? So you can install one of the following hacks to restrict debug mode to certain users/groups/IPs:
After installation, you'll have a table of template usage at the bottom of debugged page, with uncached templates highlighted.
To cache template simply edit debugged script and add template name to globaltemplates array which is usually defined at the very top of the script.
d3nnis:
Do you have access to server's shell? If so, what's output of "ls -l /proc/loadavg" and
"ls -ld /proc" ?
Anyway, you might want to revert to previous version of the hack for the time being...
Each vb3 page is getting all "cached" templates in a batch, in one SQL query. Every uncached template needs separate query to run, thus increasing load on SQL server.
To find out what templates are uncached, one have to run the script in debug mode. Of course tt could be done simply by putting $debug=1; at the beginning of the script, but you don't want to scare your users, do you? So you can install one of the following hacks to restrict debug mode to certain users/groups/IPs:
After installation, you'll have a table of template usage at the bottom of debugged page, with uncached templates highlighted.
To cache template simply edit debugged script and add template name to globaltemplates array which is usually defined at the very top of the script.