My ideal fantasy implementation would be the caching equivalent of Monolog - a nice, elegant standalone project with multiple backends which goes on to help define the PSR (IIRC!) and is then integrated into Symfony with a Bridge/Bundle. Making it a core component (as in, distributed with the Standard Edition) could potentially wait until a PSR is finalised, but BC could also be maintained with a wrapper.
In the meantime, Zend Cache and Doctrine Cache are both fine and have numerous backends (both are missing a redis backend, but both have APC(u) and Memcached support). On 3 Jun 2013, at 09:45, Matthias Noback <[email protected]> wrote: > Hi Fabien, > > It would be great to be able to exchange the filesystem cache used by most > Symfony2 caching mechanisms with something faster, by just switching a > configuration option. > This probably calls for a Cache component and many modifications made to all > existing caching mechanisms. > > When it comes to performance, I think it would be good to further analyze > dependencies of some many used classes (like event listeners) and make some > of the dependencies lazy-loading by default (using proxied services). > > Best regards, > > Matthias > > > Op maandag 3 juni 2013 08:52:30 UTC+2 schreef Fabien Potencier het volgende: > 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 [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. > > -- -- 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.
