Profiling your PHP and the SQL that is sent to the server is an
excellent way to identify sections of your code that need to be
optimized or approached differently. The nature of Cake's easy model and
association framework is ripe for sending more queries than necessary if
you aren't careful. Typically, it's not a big deal, but if you expect
traffic in the amount that might threaten performance, those are things
whose impact will increase exponentially with the load on the application.
jitka (poLK) wrote:
> Fine-tuning cake app? Do You mean besides good practices in php
> programming in general?
>
> - use some opcode cache
> - use view caching (and caching of data) as much as possible
> - don't query db for data you don't need
> - use persistent models if possible
> - use only those components ('components' in general sense) of your
> app you really need in during of every request
>
> Etc etc.
>
> Or even better: ask Cake Software Foundation for review of your
> application.
>
>
> >
>
--
Joshua Benner
http://bennerweb.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake
PHP" 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
-~----------~----~----~----~------~----~------~--~---
