I'd be interested in hearing what people have to say about this topic too. My immediate suggestion would be to use the Apache benchmark tool (ab). You could benchmark an action in your cake application which just performs a semi-random requestAction to common application functions. This will actually be more overhead than usual (as you have two full requests rather than normally one), but you can then use nice php code to determine the weighting towards which requestActions are performed, you can store some logs about performance, all that kind of jazz.
However, I do think that the main aim of Cake is rapid development, rather than best performance. I'm not saying that Cake is slow, but it is common to have 100 - 300 ms page creation times for simple actions. However, server hardware is cheap in comparison to software development / maintenance costs, so I still think it is a winning combination. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
