Just my two cents: CakePHP is fast enough for me :-) That's not to say you shouldn't optimize for speed at some point in the future. I just mean, it shouldn't be a priority.
Keep doing what your doing Cake dev's. Cake hasn't become one of the most popular PHP frameworks because of its speed ;-) On Aug 28, 4:11 pm, kiang <[EMAIL PROTECTED]> wrote: > Maybe there could be one page like 'Read first before benchmarking' in > home page since there exists many mis-understandings around the > world. :) > > --- > kiang > > On Aug 28, 10:41 pm, Gwoo <[EMAIL PROTECTED]> wrote: > > > One thing we know for sure is that we can always work to improve the > > speed. However, we will not do it in earnest until the time is right. > > We have been here before, seen similar things, and come up with the > > answers. > > > While the hello world is pretty silly, a couple of things strike me > > right off the bat. For one, var $helpers = array() will still load 3 > > files, while setting it to null will stop all loading. So, in a lot of > > ways Cake shows up slower because it does more from the start. The > > other major place is the session handling. We have no idea what his > > settings were in this regard. > > > In any case, now that we are deeper into the RC cycle you will see in > > the timeline many efforts to improve and optimize the responsiveness > > of the framework. If you would like the historical perspective have a > > look at what happened in 1.1 between the 1.1.13 and 1.1.17 releases. > > We have a history of squeezing speed out of this language and > > framework and we prepared to do it again. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
