I use Hellcat's Realtime Page Compressor... does this work with that?

I have this problem (double vBShout, Members visited today, IRC manager) too...
Any ideas?

I do too good question.... Also does this work on 3.5.3 ?

Yes it does i have them all hellcat's and pluging accelerator and pluging cache and compresssors works fine:)

Nice idea though I see two problems:

1) You could run into an endless loop trying to get a lock
2) Increased memory footprint
After some time, you've effectively cached templates for all actions.

I played with template caching myself (using APC) some time ago and didn't get any performacne increases - it even seemd to be a bit slower.

What are your experiences?

I did the same test last year, i got marginal improvements in some scripts and performance loss in others. I was relying on APC etc to cache the file into memory.

i have had no problems using it, infact it does help quite a fair bit on my forum.

Using MySQL to get a first lock, then using FLOCK to attempt a lock there is a very minimal chance of running into an endless loop; even so it would timeout eventually as there is no code to not prevent from timing out. Even so, I could add a small counter into the while loop.

The memory footprint is increased with subsequent caching, and i Discussed that with a couple of other people while deciding how i should delegate uncached templates; at first I was sorting caches by their GET request ie.

private_trackpm_1.php and so forth; the problem with this is that there is no way to tell if the do= is a valid request, and would subsequently create bogus template cache files that were based off of global headers inherent to each inclusion of ./global.php

If you have a better idea feel free to say.

ps. It is faster on my end using this system; with a better plan and support for SHM via eaccelerator/apc/ etc.. it can be increased.

private works absolutely fine on my end, as well as misc.php; theres no reason why they should be excluded.

Whats the problem exactly.

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.