and this is the tutorial i could not succeed for php cache lite
http://kevin.vanzonneveld.net/techblog/ … ache_lite/

...
i could give the code here if interested.

Please do.

Gee, I haven't run jpcache for years - I once ran it successfully on a Mambo site long ago that was on shared hosting and where no other caching would work. I remember it as reliable and effective.

and since my php is weak
i dont know if it could be dropped with PHP Cache_Lite for members even more

tried PHP Cache_Lite for registered users for only main page
i dont have enough php knowledge could not do it yet.

Indeed: without a database query, how would you know what group someone is in?

Yes. So user permissions should not be considered for this static html caching. Static html caching should be universal for all usergroups if this MOD is switched on just like WP Cache for WordPress.

    Registered users online: 2
    Guests online: 28

So it is the guests including bots who need to view the cached pages more than anyone else. Please make this MOD if you can. It will a great help for us on shared hosts.

8 queries is nothing. And it's still only one connection.

Yes, but it all builds when there are a lot of simultaneous visitors on the forum. PunBB forum pages load very fast so the visitors would browse many pages in a shorter time than other forums. So there is a chance that there may be many simultaneous database connections to the database at some point of time and that is enough for the shared host to suspend the account or for the forum to go down with errors.

As I pointed out above, I don't think a Php Cache gives exactly the same benefit as a fully static cache like WP Cache for example would because the forum pages will still execute queries to the database as per my knowledge. If that was the case, WordPress people would use only one of them at a time. But so many are using WP Cache in addition to a Php cache. I don't think it is a hassle to design such a MOD for PunBB. It will remove the hassles for those who want to run a higher volume PuBB forum on a shared host with that max db connections restriction.

I think this problem was only for a previous version of XCache and WP Cache. As far as I know, WP Cache has no reported problems with other PHP Caches.

I don't get you on this. WP Cache (which caches for reducing db load) works well with PHP Caches (which cache for reducing php load) and they both play very well together on the same shared hosting with an updated (not outdated) cache system when a post or comment is new or edited.

I am already on a paid shared hosting and that is what we are discussing about. Please read the above replies. The queries don't eat up the bandwidth. They eat up the RAM (mostly) and CPU of the shared server. I already said that paid shared hosts have a limit of 30 to 50 simultaneous database connections which is main problem. Many have faced this problem of "maximum database connections exceeded" with PunBB too on paid shared hosting. They are many topics about it on this forum. I guess one of the main purposes and advantages of designing PunBB was to make it run smoothly on a paid shared hosting also even for a high volume and visitor forum. I think that out of all popular forum scripts only PunBB is so lightweight, that it can faciltiate a high volume forum on a paid shared hosting. And with such a full static page PunBB MOD, it would allow a few thousands of simultaneous visitors on a paid shared hosting imho. Please remember than a shared hosting is less than $10 monthly while a reasonable VPS is around $50/month  and dedicated is much more. Thanks.

Dynamically update? That's not a cache, that's how things already work.

WP Cache does dynamically change only the WordPress new or edited posts or comments and again adds them to the cache.

I understand what you mean, but what I'm referring to is the fact of: how does it update the cached data? By connecting to the db and updating the cache. So in theory, you are swapping a dynamically generated page for a dynamically updated cached page. As you can guess, the difference there would be, db wise?

Caching is designed to take the load off PHP itself, not the db. If you try to achieve both, you'll end up with an outdated cache.

Just ensure something like eAccelerator, APC or Xcache are installed on your PHP setup and you will get much the same benefit as designing something akin to WP Cache for punBB, with far less hassle.

I agree, I use APC and it's great, my sites just pop and I can handle 5 times the number of users.

You honestly have to decide on one method, I've read cases where WP Cache had issues with PHP accelerators, as in handing out blank pages to users. Also, Wordpress has it's issues with a Digg effect, thus making their cache necessary where in PunBB's case you can handle the storm.