One reason cache warming was introduced are Doctrine Proxies, they NEED to be generated on the first request or otherwise you are using the auto-generate strategy which is very slow on multi user enviornments and has the risk of cache slams (granted, first request generation has the cache-slam problem also).
I only got the whole idea of cache warming when lukas complained about how proxy generation worked before that, so removing that will bring this problem up again. On Mon, 28 Feb 2011 16:42:54 +0100, Nils Adermann <[email protected]> wrote: > On 02/27/2011 11:47 AM, Lukas Kahwe Smith wrote: >> That being said what is the target audience for this feature?: >> 1) people that do not want to bother themselves to call the CLI command >> 2) people that do not have access to the CLI command >> >> I do not think we really need to deal with 1), this group should just be >> steered towards having everything generated on the fly. For 2) there >> might still be people who do care about performance, yet still are on a >> shared host without CLI access (phpBB users). Now for these they will >> need some sort of admin panel anyway to do installation of Bundle's etc >> and imho that could also be the place to put any sort of intelligence >> about cache warming via a web SAPI. > Yes indeed, it is not necessary for this kind of an installation to > automatically warm caches on first request. > > Nils -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com 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
