Just remember one thing. Don't do your benchmarks using the dev front controller. The dev controller has no caching, loads additional global variables to keep track of request/response info and other debug information. The best test is to benchmark on the production front controller as this is where users of your application will access the system with all the performance improvements intact.
On Wed, Oct 21, 2009 at 12:16 AM, roberto german puentes diaz < puentesd...@gmail.com> wrote: > Well, it’s just very initial > > The problem: Follow Practical Jobeet with Propel and Doctrine, and using > Symfony1.3, How long takes interac with a simple CRUD? > Reading the Chapters 1 and 3, for each ORM, and warp to front controller > for DEV enviorement inside a benchmark file, these is the results > > http://www.puentesdiaz.com.ar/blog/?p=167 > > I don't want start a warflame, please. It's just a simple test with > practical jobeet. It's not an absolute true. > > -- > Cr. Puentes Diaz > MP 10.12726.9 > Córdoba - Argentina > > www.puentesdiaz.com.ar/blog/ > www.puentesdiaz.com.ar/blog/novedades > www.twitter.com/puentesdiaz > Linux User n° 441474 > Ubuntu/Symfony/Eclipse Rocks! > > Sign for Free License for Project Zero > http://www.petitiononline.com/zerogpl/ > > > > -- Gareth McCumskey http://garethmccumskey.blogspot.com twitter: @garethmcc --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
