[wp-hackers] (Fwd) WP Tuner plugin alpha - useful? suggestions,
wordpress at santosj.name
Fri Jul 11 00:39:10 GMT 2008
I'm not sure I've seen code that was object oriented and procedural with
majority of usage with globals. Did you choose that because of the
performance of using globals vs properties?
Using microtime() (or was it time(), but I hope it wasn't time()) is not
the best method to tell the performance. It might tell you trouble spots
of where to look, but it is using a broad brush when you should be using
a finer one.
It is slightly funny, I made a similar plugin:
http://wordpress.org/extend/plugins/performance-testing/ with a similar
goal. Great minds must think alike eh? Or at least need breeds
invention, so on and so on.
There aren't hundreds, there are currently only two. Yours and mine
(that I know of, there might be some private ones out there) and I look
forward to what you come up with. Some of your code did give a few ideas.
One suggestion is to use the XDebug xdebug_time_index( ) to get the
time. It might give a better indicator. What I do like about your plugin
is that you don't require any extra PHP extensions that are non-standard
on most PHP installations, like mine does. However, I do think that if
someone is going to be profiling and debugging they should be using
XDebug to do so.
Webbed.Pete at gmail.com wrote:
> [I don't seem to be getting emails through the listserve. Receiving ok, but this is the
> second email I've sent. I've now re-registered. Is anyone receiving this??? Thanks.]
> Hi all,
> I'm creating my first plugin, and making some great progress. I'd like to share it as a
> "beta" with you for testing, suggestions and feedback.
> It's called WP Tuner: analyzes performance of WordPress, themes and plugins. Shows
> overall timing, and analyzes all DB queries triggered by both core and plugins. Shows
> what is slowing down your blog. Also shows server load if possible.
> Download here for now: www.ds.org/files/plugins/wptuner-0.4.zip
> I've already used this to fix some critical issues on a major blog (125k comments, zillions
> of hits).
> Some nice and/or unusual aspects of my design:
> * Mu-compatible, translatable, uninstallable
> * Self-installs, very carefully, into wp-config.php
> * Backward compatible to 2.0.6 (tested on 2.2.1, earlier via code inspection)
> * Injects itself into wpdb class on the fly (I was rather pleased with this! I
> love php :) )
> * Self-diagnoses most possible installation challenges
> * Simple presets plus custom configs
> * Developer-friendly aspects, including a nice logging capability
> * Invisible to normal site users
> Some questions I have:
> * Is this a waste of time? I don't want to publish a plugin that's already out there 100
> * My admin page is VERY ugly on older WP. I'm using the usual CSS as far as I know. Is
> it just not worth cleaning up?
> * Anything else I can/should do to make this more useful?
> The only thing NOT working AFAIK is the links to further info: me, the plugin, a donation
> tip jar. I've not yet built my own blog (but getting close). (Yes, I built this plugin before
> ever starting to blog. Mostly wanted to help a friend...)
> Your thoughts much appreciated!
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers