![]() |
No pain at all, it's a very good idea. :)
Btw, I'm counting on guys like you... that will post the actual code changes. Go ahead and post them. Thank you for helping out. EDIT: 26 queries on your front page.. aren't you affraid??? |
Or you can do like I did and re-upload the 2 files and you won't have to remember the changes then. ;)
|
TECK, how do I change the class name from "page" to "tfoot"? And what's up with the debuge mod? It says it's currently off.
Take a look - http://www.bonethugsforums.com/ |
Edit this code, inside the vBMicroStats Global Hook:
Code:
// regular users template $config['Misc']['debug'] = true; This is more like a security feature, in case you forget about it... |
Oh thanks for your support! :)
|
Is it normal for this:
Quote:
Quote:
EDIT: Well, I just had this one show up on the same page: Quote:
|
what are my numbers like re: performance
Page generated in 1.18516898 seconds (49.02% PHP - 50.98% MySQL) with 14 queries 4,182.56KB Used | DEBUG Mode OFF | GZIP ON (level 1) | NO Uncached Templates |
Bob, do you have a cache installed? That's what it generates a SQL spike...
I actually opened a ticket for this matter to vBulletin, their own code generates the same results... http://www.vbulletin.com/forum/bugs3...iew&bugid=2481 So far Scott and Freddie are looking for a solution, the bug was confirmed. The issue we are dealing with is the following: Once a query is cached, the SQL execution time (%) gets low, only the connection time and other non cached SQL processes are filtered by vBMicroStats. Then, once the queries are not in the cache anymore, BOOM, a heavy SQL demand is passed to the server. That explains the high SQL % you get sometimes. I'm in the same boat, no fix possible in my eyes, that's the way caches work. I hope vB Team will find a trick in their hat. read more in the bug thread I opened. |
No, sir, no cache installed at all. I didn't notice it on the earlier versions of this hack but then I didn't really check it that closely then. I'll wait to hear what you find out. ;)
|
Hmm. It should be stable then, except when the VB default query cache is performed.
Do this: Open a support ticket with vBulletin and ask why the query time and php time are not at all stable, all the time. They will ask you to show them the exact probem... Enable Debug Mode then let them see the explained queries. You will notice (at the end of the page in bold) that the query execution time at the end varies in a similar way, maybe a little higher then vBMicroStats. Post the ticket results for all of us. IMO, it's someting related to the server? vBMicroStats actually reads what is fed into the script, that's all. |
All times are GMT. The time now is 01:41 AM. |
Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|