Out of personal experience I can say, cakephp CAN handle sites that get allot of visitors.
I use APC for cashing, that helps allot. Ofcourse you'll always have some overhead of the framework compaired to if you only write what you need when you need it. But that'll take you a long time to write. Just use caching + the containable behavior, it's all you need :) Using cake really pays of in the end, it saves you time and it's more secure then if you write everything yourself. On Sep 22, 4:43 am, Aaron Shafovaloff <[EMAIL PROTECTED]> wrote: > Yeah, get to know the containable behavior. > > On Sep 21, 12:35 am, toby78 <[EMAIL PROTECTED]> wrote: > > > I am currently evaluating different frameworks and also looking at > > cakePHP. > > > My first thought was that it seems not very efficient... > > > If you have an object, e.g. "User" that has other related objects such > > as "Message" or "Photo" - there will be SQL statements to select all > > content from all related tabled - no matter whether it is used or not. > > > If you have a large database table this could also lead to problems as > > the query is not pages, but everything is selected at once? > > > There also does not seem to be a caching of database queries? > > > Or is this possible? And if so, how do you define which queries are > > cached in which intervall? > > > Thanks! > > > Toby > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
