[pLog-svn] A terrible truth about plugin

Jon Daley plogworld at jon.limedaley.com
Fri Feb 1 14:53:50 EST 2008

On Sat, 2 Feb 2008, Mark Wu wrote:
> For my #1 test , my anti virus program still turned on. It really annoying.
 	Ah, that makes sense.

> It might help to get the plugin menu entries put into menu.xml and put the
> plugin locales into core locale files..... they just save at least 200ms in
> each request. Not bad :)
 	I suppose that is why some other programs have their plugins do 
just that - directly edit core files, etc.  And then it is just about 
impossible to uninstall stuff.  I really like our setup where everything 
is clearly separated.  The include thing for the locale makes sense, 
though I don't have a feel for how that will affect the performance.
 	I'd rather look into a different XML parser, or perhaps changing 
the plugin api to make all of the menu additions happen at once (maybe a 
callback sort of thing?) rather than multiple passes through the table.

> For index page, I think it is not a serious problem, because we have a very
> good page cache here.
 	Yes.  I have wondered about having a cache on the admin side too. 
I had similar results with squid that Ayalon had with varnish that you 
can't blindly cache everything.  But, it seems that we should be able to 
do a decent job from inside.

 	By the way, you are testing 1.2.6, and not 2.0, right?  You might 
try looking at 2.0 and see if there is any interesting differences.

More information about the pLog-svn mailing list