If you use good caching of expensive database requests, and offload static files to a CDN there is no need to bother with full page caching for most sites.
Our CMS with warm caches can display a somewhat complicated page in about 100-200 ms ... /thomas On 29 Jul 2014, at 12:22, HK <[email protected]> wrote: > Why isn't needed? Why do I have to bother the server with more proccessing? I > have for example a (medium size) VPS with 40+ domains. Some of them use > cakePHP, and hopefully more in the future. > While each site is rather small (some with many pageviews though) all of them > are hosted on the same server. > > Moreover you can achieve less page load times which IS crucial for visitors, > SEO, etc. > > On Tuesday, July 29, 2014 1:07:01 PM UTC+3, José Lorenzo wrote: > For those small sites, is having full page cache actually needed? I would > guess that performance wouldn't be a big concern in those cases > > On Tuesday, July 29, 2014 11:47:16 AM UTC+2, HK wrote: > For small sites that I develop is very helpful. The need to > use/configure/monitor extra software like varnish is pain in the ass, > especially if you don't have big sites to host. > > On Tuesday, July 29, 2014 11:28:17 AM UTC+3, José Lorenzo wrote: > HK why would you miss it? There will be no replacement for the cache helper. > We recommend using Varnish, which provides the ESI tags. They are similar to > the cache tags but they involve internally doing another request. We think > this is a more robust and scalable solution than doing it in PHP. > > On Tuesday, July 29, 2014 9:06:36 AM UTC+2, HK wrote: > Too sad to hear cache helper is removed. This ESI based replacement is it > going to be in stable 3.0 version? > > On Monday, July 28, 2014 10:13:14 AM UTC+3, José Lorenzo wrote: > > CacheHelper has been removed from CakePHP. The core team feels that the > functionality this helper provided is best handled by standalone servers like > Varnish. While we explored building a ESI based replacement for CacheHelper, > there were a number of edge cases that would have complicated the > implementation. > > > > -- > Like Us on FaceBook https://www.facebook.com/CakePHP > Find us on Twitter http://twitter.com/CakePHP > > --- > You received this message because you are subscribed to the Google Groups > "CakePHP" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/cake-php. > For more options, visit https://groups.google.com/d/optout. -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are subscribed to the Google Groups "CakePHP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/cake-php. For more options, visit https://groups.google.com/d/optout.
