Re: CakePHP not recommenable for busy websites?

2008-09-22 Thread Crazy

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
-~--~~~~--~~--~--~---



Re: CakePHP not recommenable for busy websites?

2008-09-22 Thread mbavio

I believe that CakePHP can handle big/huge websites, but using the
Mozilla Add-ons as an example is not a trully example. Why? Mozilla
add-ons uses a very modified version of Cake 1.1, if you dont believe
me, check app_model of it. Also, I think it uses Zend too. So, there
HAS to be a better example than that.

Cheers,
mbavio

On Sep 21, 9:19 pm, Nate [EMAIL PROTECTED] wrote:
 http://book.cakephp.org/view/510/Sites-in-the-wild

 Take special note of the Mozilla Add-ons portal, one of the most
 heavily trafficked in the world.

 On Sep 21, 2: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
-~--~~~~--~~--~--~---



Re: CakePHP not recommenable for busy websites?

2008-09-21 Thread Zac Tolley

Not only can u cache but In the find function use can set how deep the  
result goes and I find this actually results in ability to have fine  
tuned lean db access

Sent from my iPhone

On 21 Sep 2008, at 07:35, 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
-~--~~~~--~~--~--~---



Re: CakePHP not recommenable for busy websites?

2008-09-21 Thread Novice Programmer
Then there are bind/unbind model plus the new containable behavior to let u
select the columns in the query..

thanks.

On Sun, Sep 21, 2008 at 8:03 PM, Zac Tolley [EMAIL PROTECTED] wrote:


 Not only can u cache but In the find function use can set how deep the
 result goes and I find this actually results in ability to have fine
 tuned lean db access

 Sent from my iPhone

 On 21 Sep 2008, at 07:35, 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
 
  

 



-- 
Thanks  Regards,
Novice.

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---



Re: CakePHP not recommenable for busy websites?

2008-09-21 Thread Nate

http://book.cakephp.org/view/510/Sites-in-the-wild

Take special note of the Mozilla Add-ons portal, one of the most
heavily trafficked in the world.

On Sep 21, 2: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
-~--~~~~--~~--~--~---



Re: CakePHP not recommenable for busy websites?

2008-09-21 Thread Aaron Shafovaloff

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
-~--~~~~--~~--~--~---