Even built-in file caching can be pretty quick depending on how much uniqueness there is between page refreshes. The page cache read occurs very early on in the Cake process. (I still wish that the built-in page caching allowed for keying off more unique properties besides the URL such as cookies or session data but I'll live...)
On Tue, Jul 1, 2008 at 12:26 PM, RichardAtHome <[EMAIL PROTECTED]> wrote: > > Thanks for the reply Tarique. > > I'm about to start looking into using APC cache or some other op-code > caching too, does anyone have any experience with using an op-code > cache with Cake? Any gotchas I should be aware of? > > On Jun 30, 10:49 am, "Dr. Tarique Sani" <[EMAIL PROTECTED]> wrote: >> On Mon, Jun 30, 2008 at 3:11 PM, RichardAtHome <[EMAIL PROTECTED]> >> wrote: >> >> >> >> > Does anyone have any tips, techniques or experience about best >> > practices for managing a potentially large visitor spike without the >> > box catching fire? >> >> Cache! cache!! and more cache!!! that is provided you have done everything >> else to optimize your app. >> >> The meltdown usually occurs because of the PHP <- > MySQL pipe getting >> choked >> >> Tarique >> >> -- >> ============================================================= >> Cheesecake-Photoblog:http://cheesecake-photoblog.org >> PHP for E-Biz:http://sanisoft.com >> ============================================================= > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
