I always find it interesting how benchmarking is done. My understanding of software development is to define some requirements, write some test, run the test, write code to support the test, once all test for given requirements iteration are passing, then we look at profiling. In all my years of writing code, I can't tell you how much time some of our jr developers have wasted trying to improve the performance of a piece of code before the requirement are finished, almost in every case the module they were trying to increase performance on was one that is seldom called and not an issue for the intended purpose of the app.
People don't bother profiling your app until you are done with your requirements. The point of a framework is to speed up time to deployment. The trade off is going to be some overhead and speed. CakePHP has definitely done this for me, and when I get to the profiling portion, and I find something I can't live with in the cake framework, I'll write some custom code to deal with that speed issue. But I'm guessing since this is a web app, my biggest profile job will be the 14 steps of yslow, and isn't it nice that cakephp is capable of dealing with most of them, and Apache deals nicely with the others. Bake on! On Aug 28, 12:32 pm, majna <[EMAIL PROTECTED]> wrote: > .. and cake hello world application memory usage is 5 Mb. > So when you put few things more (model recursive instances) you must > fight to be below PHP4 default 8Mb. > (For exmpl. CI has 1.2 Mb.) > (persistModel and which caches class registry use even more memory) > (profiling cake I can see around 2000- 3000 calls to PHP's strtolower > etc.) > > On Aug 28, 5:48 pm, Nate <[EMAIL PROTECTED]> wrote: > > > @kiang: That's a great idea. I think a more general performance- > > tuning guide would really help out. I know there are some resources > > on this, but I think a comprehensive guide in the Cookbook somewhere > > would be great. I'll see what we can do about this. > > > On Aug 28, 11:11 am, 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 -~----------~----~----~----~------~----~------~--~---
