Hi, Great 2.3 is being released. Performance is very important, create the suite of benchmarks is the right start.
So i will throw two ideas: 1) Some "lib" of string util and inflector, we have methods like camelize on container (that don't belong there), In my opinion we should have in inflection something like this: http://book.cakephp.org/2.0/en/core-utility-libraries/inflector.html and on string util a lot of useful stuff can be don -- 2) A component that I miss a lot, and I probably will develop it internal to my organization, a cache component, but not any cache component, a cache component with distribution and sharding from start, for example memcached php lib have distribution (consistent hashing, modulo, etc), I think one of php redis lib have it two. I was waiting FIG to approve the cache PSR to follow something, but probably cannot wait for it more. The difference of this cache component to all the are already there developed is the focus on scaling horizontal, php cache libs there are a lot but done thinking in a shared nothing architecture, I can't find one. Main points: - distribution, with some out the box like consistent hashing and modulo, but possible to define new ones; - 100% OOP, for example Zend cache: getItem(string $key, boolean & $success = null, mixed & $casToken = null) instead should be getItem(string $key) and return one object with value, success or not and so on - should be very easy to add support to other data stores and clear documented - tags - "below" if possible try to reuse most code as possible using clients already developed, eg: redis for example phpredis or predis 2013/6/3 Fabien Potencier <fabien.potenc...@gmail.com> > Hi all, > > As Symfony 2.3 is going to be released today, that also means that work on > 2.4 can start now. > > We have 4 months of development, so if there is anything that you think we > need to work on (or things that you want to contribute to), that's the > right time to discuss it. Based on the topics that are the most popular, we > might then create dedicated teams that focus on them. > > Besides the few pull requests that already target 2.4, I have one topic > that I want us to work on for 2.4: **performance**. What can we do to > improve the performance of Symfony (on real-world apps, not for a simple > hello world page)? What are the main pain points? The first step would be > to create a suite of benchmarks for the critical components > (HttpFoundation, HttpKernel, Routing, EventDispatcher, ...), and then see > how times can be improved. > > So, if Symfony 2.4 was just about 1 new major change, which one would it > be for you? > > Fabien > > -- > Fabien Potencier > SensioLabs CEO - Symfony lead developer > sensiolabs.com | symfony.com | fabien.potencier.org > +33 1 40 99 80 80 > > -- > -- > 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 symfony-devs@googlegroups.com > To unsubscribe from this group, send email to > symfony-devs+unsubscribe@**googlegroups.com<symfony-devs%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/**group/symfony-devs?hl=en<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 > symfony-devs+unsubscribe@**googlegroups.com<symfony-devs%2bunsubscr...@googlegroups.com> > . > For more options, visit > https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> > . > > > -- *Eduardo Oliveira * *IT* ***Email:* eduardo.olive...@adclick.pt *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 symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com 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 symfony-devs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
