How are you going to measure the performance? The time it takes to process a request? The time it takes to develop? Are you going to implement caching? Are you going to try multiple datasources (of various types)?
IMO, a real-world app should have the following features: - User registration - Authentication - Database interaction - At least 5 models, which cover various types of associations - Data validation - Security - Session management - Web service API (at least provisioning) - Administrative interface On Nov 5, 5:11 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > I'm writing my computer science masters thesis about PHP-frameworks. > All performance tests I've been able to find use "hello world"- > application. I'm planning to code a test application with few > frameworks. What kind of application it should be? What would you > think are the essential requirements to get a fair results of each > framework's performance? > > Currently I'm comparing CakePHP, Codeigniter, Symfony and Zend > Framework. Do you those are the essential ones? > > -Kalle > > On 28 loka, 19:39, mark_story <[EMAIL PROTECTED]> wrote: > > > On Oct 27, 9:38 pm, teknoid <[EMAIL PROTECTED]> wrote: > > > > Here's a test... > > > > Create a file index.html in the web root of your server with the > > > content "hello world". > > > Now take any framework and compare the speed it takes to render... the > > > index.html framework beats them all! > > > index.html framework is by far the best clearly! Forget this CakePHP > > crap, I'm going all index.html framework from now on. > > /sarcasm > > > I would like to see some development benchmarks as well, that would be > > interesting. How long it takes to build an example non 'hello world' > > app in each of these frameworks. Like teknoid said, servers are cheap > > man months are not. So this benchmark could be more useful for people > > choosing frameworks. With the example teknoid gave, it would take 16 > > years of CakePHP hosting to equal index.html framework development > > time. > > > -Mark > > > > On the other hand we can do another test... > > > > Take CakePHP and develop a fully functional application with 60 models > > > (or so) in two months. To double it'sperformancewe purchase a > > > dedicated server for $119/month. > > > Or we could write one from scratch in about 4 months (if we're lucky), > > > which means that we've spend 320 extra hours of development time (40 > > > hrs per week * 8 extra weeks) at $75/hr.. which translates to extra > > > $24,000 spent on the project. > > > > I'm not really sure, which one of these tests is more pointless ... > > > but to me it seems silly to measure a framework'sperformancewith > > > "hello world". > > > > On Oct 27, 12:04 pm, "wahyu setianto" <[EMAIL PROTECTED]> > > > wrote: > > > > > I have read inhttp://www.yiiframework.com/performance, it is true ? i > > > > know > > > > that CI is faster than cakephp because CI is not using OOP actualy > > > > > -- > > > > Octopus > > > > East Java Baker > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
