> Benchmark testing should be done with non-trivial code, and given these > frameworks abstract databases, and that abstraction can affect > performance, it should probably include tests that include database access.
I agree. We don't know if the tester tried a business application, then saw his framework performed poorly and then changed the terms of the test so that his framework would perform best. A business application such as a blog would best represent the performance people are looking for. Also, with the cost of hardware dropping everyday. A framework designed purely for performance will become outdated as other more complex "slower" frameworks offer better features and return on development costs. A well designed framework no matter how slow its internals can be improved without affecting the functionality of the application the framework is driving. Something that the Cake team can address with maintenance releases to address performance. With all that said, I do believe Cake is one of the slower frameworks. The extensive use of for/loops during dispatching and rendering of views has to impact performance, but the level of performance impacted depends on the implementation of the website. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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 -~----------~----~----~----~------~----~------~--~---
