Board Optimization - vBMicroStats

This hack will add at the bottom of each vBulletin (powered) page, the statistics listed below.
Also, it will help you troubleshoot and optimize your vBulletin board by viewing or comparing PHP/MySQL options and other statistics that are normally hidden in your forum pages.

Regular Users:
? Load time of specified page in microseconds
? Number of queries executed
? PHP percent page usage
? MySQL percent page usage

Administrators Only:
? Active users browsing the forum (members and guests) new in 1.1.0
? Server memory usage per page (in Kb)
? Display DEBUG mode status
? Browser GZIP library compression status
? Server average loads
? Uncached templates (useful to troubleshoot the code)

The code modifications were tested into a clean installed vBulletin board. They work 100%.
The hack was tested in vBulletin 3.6.4 and 3.6.5.
If you want to test it into a lower version (3.6.x), let me know.
Also, if you encounter any problems, feel free to post your questions here.

Step by step install instructions are posted into readme.html file.
In order to perform an efficient modification of your files, I recommend you to use Komodo Edit or Textpad.
Both editors will allow you to complete all steps without any coding errors.

The code changes are very safe and designed not to interfere in any way with the vBulletin performance/functionality.
Make sure you modify, save and upload one file at the time to your server.
Then, simply run the product-vbmicrostats.xml file.

[high]The PLUGIN itself is DISABLED by default.[/high]
This was done in order to make sure you properly edit your code first and to avoid surprises.
You will need to enable it, once your code modifications are completed:
Plugins and Products > Manage Products > vB Microstats > Enable (dropdown)
Then, go to your vBulletin Options, click on BB MicroStats setting group and set all your options.

Upgrade to version 1.0.2.
Upgrade to version 1.0.3.
Upgrade to version 1.1.0.

Want to be a guinea pig and try this hack into a higher vBulletin version?
Post your results, so others can read your feedback.

[KURTZ]

edit: OK installed on Beta 4 ...

so now i've a question:

Page generated in 0.99168205 seconds (-42.68% PHP - 142.68% MySQL) with 15 queries

i've a really slow forum ... what means this result? TIA

[KURTZ]

someone can help me? it's normal that the loading of my forum goes all on the mysql?

another Q: when i turn on the debug mode i don't see anything new ...

[SEOvB]

No, its some other modification you've got installed causing that problem

I just installed on 3.7b4 with a few other modifications and i've only go 9-10 queries on all pages.

[mark|3]

This product is not compatible with version 3.6.8 of vBulletin. (Compatible starting with 3.6.4 / Incompatible with 3.6.8 and greater)

I keep getting this error message. anyway to resolve this error?

thank

[haytham]

I am getting between 49 to 57 queries on my forum and I have 3.6.8..although it's loading fine.

[TECK]

Originally Posted by mark|3

This product is not compatible with version 3.6.8 of vBulletin. (Compatible starting with 3.6.4 / Incompatible with 3.6.8 and greater)

I keep getting this error message. anyway to resolve this error?

thank

When I released the code, it was for vBulletin 3.6.5 version.
Now, go read the product description. It is marked in bold what to do.

[TECK]

Originally Posted by haytham

I am getting between 49 to 57 queries on my forum and I have 3.6.8..although it's loading fine.

Basically, you are KILLING your server. Uninstall ASAP all the hacks you added to your board.

[mark|3]

hi i managed to installed and activate the product after changing the max variable to 3.6.9
but somehow its not displaying the relevant details on my forum. any idea why?

[TECK]

Hi Mark,

Did you enabled the plugin? Please read the product instructions, listed above the screenshots.

[Boofo]

I had this happen to me today but it turned out I was working on a hack and I added something to a plugin that it vb didn't like. Once I disabled that plugin the microstats showed back up.