You need to define define 'big application' - Number of tables, rows,
users, connections (bandwidth) or all of the above?
For large numbers of tables, Containable is your friend. For the
others, Cake is unlikely to be your primary cause of concern. Good
database design and a replication strategy would be great places to
start.
Apologies, I can't remember who's sig it is, but the best advice I've
heard on the topic is: "Just build it, damnit!"
~GreyCells
On Apr 28, 12:06 pm, keyurvaghani <keyurvagh...@gmail.com> wrote:
> Hello folks,
> Can anybody please let me know what should be taken care for better
> perfomance for site becuase it seems for developing large application
> there might perfomance issue arise with cake 1.2. As i m going to
> develop big application in and i m really wanted to know more
> regarding perfomance for working with cake.
>
> Likewise somewhere i have read that it not to use $uses instead of use
> model chain or loadmodel() if it requre. so i m seeking more and more
> tips.
>
> Thanks a lot in adavance !
>
> Best regards
> Keyur
--~--~---------~--~----~------------~-------~--~----~
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 cake-php+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
No comments:
Post a Comment