I agree that in general frameworks cannot be measured equally in benchmarks, but as long as the title of the Symfony website says: "High Performance PHP Framework for Web Development", any concern regarding performance should be investigated and not treated as an offense IMO...
Kepten On Tuesday, May 7, 2013 4:24:35 PM UTC+2, Giulio De Donato wrote: > > > Albert Casademont Filella <[email protected] <javascript:>> It has > sense? > > Benchmarks different frameworks are for those who doesn't know anything > about frameworks, practices and methodologies, > and wants a simple number in order to have something easy and quick to > learn and to share. > definition: > Benchmarking(1) = find a number in order to say 'COOL' > Benchmarking(2) = easy way to get few visitors > > sorry for the rant > > > On Fri, May 3, 2013 at 9:55 PM, Benjamin Eberlei > <[email protected]<javascript:> > > wrote: > >> Benchmarks are totally useless imho. >> >> 1. The symfony2 that is used in this benchmark is a standard edition with >> a bunch of stuff installed, for example the security component running in >> front of all requests, AOP, Di and FrameworkExtra bundles etc. Comparable >> to all the other PHP frameworks that probably don't have this enabled by >> default, its obvoiusly a drawback. Removing that stuff makes requests run >> in 12ms on my machine, increasing the performance compared to the full >> configuration by 50% and into the range of other full stack php frameworks. >> >> 2. If you look carefully, increasing the number of DB queries per >> request makes php look better vs ruby and python alot. Django being much >> behind, Rails and Symfony being on the same level. So Why care about JSON >> only serialization requests? Completely useless hello world benchmark >> example. >> >> 3. The benchmarks show Symfony doing 80-170 requests per second. Who >> actually needs so many PHP Requests per second? With HTTP Caches and all, >> you barely need that for most of the apps you are building. Symfony + ORM >> apps consistently deliver <= 200ms unless the programmer did something >> seriously wrong. I don't care about having more performance in 95% of the >> cases. >> >> >> On Fri, May 3, 2013 at 11:18 AM, Eduardo Oliveira >> <[email protected]<javascript:> >> > wrote: >> >>> "If you base your framework comparison on hello-world examples, you're >>> doing it wrong." >>> >>> Is a general benchmark, is very difficult to benchmark >>> complicate scenarios. Each one needs to benchmark against its uses >>> cases. >>> >>> Marco if the environment to run the benchmark, it can be suggested here: >>> https://groups.google.com/forum/?fromgroups=#!forum/framework-benchmarks >>> >>> I'm very interest in the results with the right environment >>> >>> Eduardo Oliveira >>> >>> >>> 2013/5/3 Matt Robinson <[email protected] <javascript:>> >>> >>>> Benchmarks are always contentious, and they obviously only focus on one >>>> tiny facet of using a framework, which is the hosting performance of it - >>>> ignoring development, debugging, etc etc. So yes, obviously worth taking >>>> with a fistful of salt, however I don't think all the tests are >>>> hello-worlds, and Symfony didn't do too well on those either. >>>> >>>> Shocked to hear that they're testing the dev environment; if that's >>>> true, what's the point of that? Nuts. >>>> >>>> On 3 May 2013, at 09:58, Marco Pivetta <[email protected] <javascript:>> >>>> wrote: >>>> >>>> If you base your framework comparison on hello-world examples, you're >>>> doing it wrong. >>>> >>>> Additionally, those benchmarks (currently) use the development >>>> environment of sf2 (without compiled DIC), and that's obviously really >>>> slow. >>>> >>>> Marco Pivetta >>>> >>>> http://twitter.com/Ocramius >>>> >>>> http://ocramius.github.com/ >>>> >>>> >>>> On 3 May 2013 10:19, Albert Casademont Filella >>>> <[email protected]<javascript:> >>>> > wrote: >>>> >>>>> For the record, here is a nice framework comparison...pretty >>>>> disappointing :( >>>>> >>>>> http://www.techempower.com/benchmarks/#section=data-r4 >>>>> >>>>> >>>>> On Wed, Apr 24, 2013 at 6:38 PM, Albert Casademont Filella < >>>>> [email protected] <javascript:>> wrote: >>>>> >>>>>> Totally agree, I wasn't even aware of this performance issue, thanks >>>>>> for bringing it up in the list. Gonna do some comparison between 2.1 and >>>>>> 2.2 >>>>>> >>>>>> >>>>>> On Tue, Apr 23, 2013 at 11:07 AM, Rob Jensen >>>>>> <[email protected]<javascript:> >>>>>> > wrote: >>>>>> >>>>>>> Hi there, >>>>>>> >>>>>>> Firstly thanks to all the symfony2 contributors for all their hard >>>>>>> work on the project. >>>>>>> >>>>>>> In response to Symfony 2.3 What's >>>>>>> next<http://symfony.com/blog/symfony-2-3-what-s-next>I think it would >>>>>>> be nice to see a focus on performance, especially >>>>>>> considering this is a long term support release. There is a discussion >>>>>>> taking place around this issue on >>>>>>> github<https://github.com/symfony/symfony-standard/issues/464>. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Cheers, >>>>>>> >>>>>>> Rob >>>>>>> >>>>>>> -- >>>>>>> -- >>>>>>> If you want to report a vulnerability issue on Symfony, please read >>>>>>> the procedure on http://symfony.com/security >>>>>>> >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "symfony developers" group. >>>>>>> To post to this group, send email to >>>>>>> [email protected]<javascript:> >>>>>>> To unsubscribe from this group, send email to >>>>>>> [email protected] <javascript:> >>>>>>> For more options, visit this group at >>>>>>> http://groups.google.com/group/symfony-devs?hl=en >>>>>>> --- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "Symfony developers" group. >>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>> send an email to [email protected] <javascript:>. >>>>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> -- >>>>> -- >>>>> If you want to report a vulnerability issue on Symfony, please read >>>>> the procedure on http://symfony.com/security >>>>> >>>>> You received this message because you are subscribed to the Google >>>>> Groups "symfony developers" group. >>>>> To post to this group, send email to >>>>> [email protected]<javascript:> >>>>> To unsubscribe from this group, send email to >>>>> [email protected] <javascript:> >>>>> For more options, visit this group at >>>>> http://groups.google.com/group/symfony-devs?hl=en >>>>> --- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Symfony developers" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected] <javascript:>. >>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> -- >>>> If you want to report a vulnerability issue on Symfony, please read the >>>> procedure on http://symfony.com/security >>>> >>>> You received this message because you are subscribed to the Google >>>> Groups "symfony developers" group. >>>> To post to this group, send email to >>>> [email protected]<javascript:> >>>> To unsubscribe from this group, send email to >>>> [email protected] <javascript:> >>>> For more options, visit this group at >>>> http://groups.google.com/group/symfony-devs?hl=en >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "Symfony developers" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected] <javascript:>. >>>> For more options, visit https://groups.google.com/groups/opt_out. >>>> >>>> >>>> >>>> >>>> -- >>>> -- >>>> If you want to report a vulnerability issue on Symfony, please read the >>>> procedure on http://symfony.com/security >>>> >>>> You received this message because you are subscribed to the Google >>>> Groups "symfony developers" group. >>>> To post to this group, send email to >>>> [email protected]<javascript:> >>>> To unsubscribe from this group, send email to >>>> [email protected] <javascript:> >>>> For more options, visit this group at >>>> http://groups.google.com/group/symfony-devs?hl=en >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "Symfony developers" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected] <javascript:>. >>>> For more options, visit https://groups.google.com/groups/opt_out. >>>> >>>> >>>> >>> >>> >>> >>> -- >>> *Eduardo Oliveira >>> * *IT* >>> ***Email:* [email protected] <javascript:> *Web: * >>> www.adclickint.com ** <http://www.adclickint.com/> >>> >>> * >>> *AVISO DE CONFIDENCIALIDADE: Esta mensagem (incluindo quaisquer anexos) >>> pode conter informação confidencial ou legalmente protegida para uso >>> exclusivo do destinatário. Se não for o destinatário pretendido da mesma, >>> não deverá fazer uso, copiar, distribuir ou revelar o seu conteúdo >>> (incluindo quaisquer anexos) a terceiros, sem a devida autorização. Se >>> recebeu esta mensagem por engano, por favor informe o emissor e elimine-a >>> imediatamente. Obrigado. >>> >>> DISCLAIMER: This message may contain confidential information or >>> privileged material, and is intended only for de individual(s) named. If >>> you are not in the named addressee, you should not disseminate, distribute >>> or copy this e-mail. Please notify the sender immediately by e-mail if you >>> have received this e-mail by mistake and delete it from your system. Thank >>> you. >>> <http://www.adclickint.com/> >>> <http://www.adclickint.com/> >>> >>> -- >>> -- >>> If you want to report a vulnerability issue on Symfony, please read the >>> procedure on http://symfony.com/security >>> >>> You received this message because you are subscribed to the Google >>> Groups "symfony developers" group. >>> To post to this group, send email to [email protected]<javascript:> >>> To unsubscribe from this group, send email to >>> [email protected] <javascript:> >>> For more options, visit this group at >>> http://groups.google.com/group/symfony-devs?hl=en >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "Symfony developers" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected] <javascript:>. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >> -- >> -- >> If you want to report a vulnerability issue on Symfony, please read the >> procedure on http://symfony.com/security >> >> You received this message because you are subscribed to the Google >> Groups "symfony developers" group. >> To post to this group, send email to [email protected]<javascript:> >> To unsubscribe from this group, send email to >> [email protected] <javascript:> >> For more options, visit this group at >> http://groups.google.com/group/symfony-devs?hl=en >> --- >> You received this message because you are subscribed to the Google Groups >> "Symfony developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > > > -- > __________________liuggio_________________________________ > > __/|_ We reject kings, presidents and voting. > /o ) \/ We believe in rough consensus > )__ v _/\ and running code (I.E.T.F. credo) > ______________________________________________________________ > -- -- If you want to report a vulnerability issue on Symfony, please read the procedure on http://symfony.com/security You received this message because you are subscribed to the Google Groups "symfony developers" 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/symfony-devs?hl=en --- You received this message because you are subscribed to the Google Groups "Symfony developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
