Hello tempor, have you found any differences between the two? I am also curious to find out what it the major difference apart from the fact that one controls the server CPU usage and the other doesn’t.
I have also notice that you are also using DB Cache Reloaded Fix in combination. Is this still working for you?
Kind regards
Thread Starter
tempor
(@tempor)
Hi mbrsolution,
I haven’t used the old hyper cache again since it was broken (it was abandoned at the time) so I cannot offer you any comparison between the two.
Hyper Cache Extended has a field which allows you to define a point at which either the cache generation or the cache mechanism is turned off (it is not defined by the author which of the two).
Concerning the Hyper Cache Extended + DB Cache Reloaded Fix combo it still rules my friend. Some tips from my experience though:
-For Hyper cache you get the best benefits if you configure it for very very long expiring times (months). CMS sites get the most benefit.
-For the db cache you really feel the difference the more dynamic the site is (meaning more DB queries). It is still helping in a CMS enviroment.
Best regards
