While looking at the code fast ... Basically, the plugin accelerator writes all exististing installed plugins to files. Then, it reads TWICE(instead of once) ALL(instead of only the needed) newly created hook/plugin files, every time you access a forum page. In other words, you process a lot of unnecesary data. Since when reading many files in block is faster then reading a small piece of data from a database table? I might be wrong, since I only examined the class included in the plugin files... Feel free to comment on this, we are here to learn, not to put down other coders.
Why not just leave it the way it is made by vBulletin and install eAccelerator or APC?
eAccelerator, on top of caching the queries, it optimizes the PHP code also...
Well, I see several problems with that addon, don't even know where to start. I would not recommend using that at all since it can essentially ++++ up your installation. What happens if you insert some bad code in for example the global hook? You can't even disable that addon anymore then. Then you have to make all your files world writable. I'll add a note that using this plugin is not recommended with this extension.
TECK: As far as I can see, the plugin accelerator plugin writes the plugins INTO the official vBulletin files INSTEAD of the hook calls. So you basically end up hacking the offcial vBulletin files. Meaning when something goes wrong you can reinstall vBulletin. The problem is that APC/eAcc doesn't cache eval().
What I DO recommend is when you're having a lot of plugins move the code to an external .php file and include that one at the global hook. I have a 20kb plugin.php with all my php code in it, I only add if's and function calls to the actual plugins.
Well, I see several problems with that addon, don't even know where to start. I would not recommend using that at all since it can essentially ++++ up your installation. What happens if you insert some bad code in for example the global hook? You can't even disable that addon anymore then. Then you have to make all your files world writable. I'll add a note that using this plugin is not recommended with this extension.
TECK: As far as I can see, the plugin accelerator plugin writes the plugins INTO the official vBulletin files INSTEAD of the hook calls. So you basically end up hacking the offcial vBulletin files. Meaning when something goes wrong you can reinstall vBulletin. The problem is that APC/eAcc doesn't cache eval().
What I DO recommend is when you're having a lot of plugins move the code to an external .php file and include that one at the global hook. I have a 20kb plugin.php with all my php code in it, I only add if's and function calls to the actual plugins.
Ive been using it with yours and everything seems fine
Well just see this extension, instead of putting all the PHP code into a plugin I move it to template_cache.php and just add a few lines to the plugins.
Well just see this extension, instead of putting all the PHP code into a plugin I move it to template_cache.php and just add a few lines to the plugins.
It's pretty easy.
He's having a master code static page, probably separated in functions.
Then, he calls the specific functions in plugin, with one line of code. Faster.
It's pretty easy.
He's having a master code static page, probably separated in functions.
Then, he calls the specific functions in plugin, with one line of code. Faster.
Plugin Based Template Cache Details »»
About Developer
Visit Web Site
Uses Plugins 
No support by the author.
05-17-2006, 01:37 PM
