WP Tuner 0.9.3: User Hints & Questions
This is the archive of comments for WP Tuner 0.9.3.
This release contained several important improvements:
- Thanks to user feedback, I dug in carefully and found (and worked around) a bug in WordPress. The admin user in a new install does appear to have admin privileges if the traditional ($user_level) test is done.
- I found a way to work around the reduced functionality in older WordPress releases that made it hard to display good CPU timing for each part of WordPress processing.
- I added support for the more unusual MySQL queries. And, if a query is not recognized, its location is identified.
reply and
paste link
November 23rd, 2008 at 12:02 pm
Hi again,
Thank you for all your help. After updating it to v0.9.3 it is working. Would be nice to have some documentation on how to read and fix the problems.
Shimshon
reply and
paste link
November 24th, 2008 at 1:02 pm
Hi there,
The report I get places 94% of the time on the Start process with around 28 seconds (!).
Now it might be true. Question is - where do I go to further investigate the problem?
Thanks,
Tsahi
reply and
paste link
November 24th, 2008 at 1:12 pm
Shimshon (#1), I will be adding more documentation in the days to come, including more blog postings here. In general, problems fall in one of four categories:
* Query errors that cause trouble: either get the plugin maker to fix it, or find a different plugin.
* Slow plugins: either get the plugin maker to fix it, or find a different plugin
* Slow overall: this could be a configuration problem on your site, or a problem with your host
WOW, Tsahi Levent-Levi (#2), 28 seconds is a VERY long time!
For now, your next step is to follow the hints in the readme about hand-inserting extra WP Tuner calls into wp-settings.php — you can break down that time into smaller chunks, to see if it is one of your plugins, or your basic startup code.
I have just released interim version 0.9.4 (0.9.5 will contain updated translations.) 0.9.4 fixes all outstanding bug reports.
There will be a delay before the next release. I am working out how to automagically determine the time spent in each plugin, widget and theme code. That way, I can give you a very simple interface that shows specifically which bits are slow and which are fast… so you can decide what to do about it! This won’t be easy… so for now, “hand patching” is the only way to go.