Trigunflame |
03-17-2006 06:42 PM |
Quote:
Originally Posted by Scott MacVicar
Your best not to store it in eaccelerator manually as you will get overhead for the unserialize calls for a large template array, storing it in files is the best way.
You should be able to use $_templatedo so that you cache the correct set of action templates, though personally I would create a single global cache file with the ones present in global.php and then a script / action specific cache.
Regarding uncached templates, why not look through the value of $vbulletin->templatecache at the end of script execution.
I have several designs for a potentially better system if you want to investigate.
|
I havnt actually benchmarked any of the shared memory functions for serialization/unserialization speed but i dont believe the overhead is that great on 5.1+, i know the bug for 4.3.9 was fixed a while back; bug #31332 actually.
Hence the reason why I defaulted to to files at first; although there is stat call overhead which actually has been removed in cvs a while back.
This system definately needs to be further refined though, Ive managing many things at once.. so I still have a lot to do at once.
|