Matthias Nothhaft wrote: > As I mentioned in a posting before: Saying the filter chain is evil is a > bit too simple..
Of course :) > We have to separate the problems: The filter chain is a concept that is > pretty smart IMHO. But the implementation (namely the filters) could get > some optimizations like lazy loading. Yes! > Also the sfController::forward() has much overhead that is not needed > with each request / forward. Yes, there needs to be more control over which filters get re-executed etc. when you call forward(). > What I see is that if we change something here we should separate > between a) request and b) module/action call Yes! >> 4) configuration loading (sfOptimizer is a scary approach, see my recent >> post on symfony-dev@ on my micro benchmarks) > > I wonder how we can check these things reliable. xdebug :) > The other way is to use external tools like ab or siege which is > probably a more reliable approach but with the drawback that it is hard > to examn isolate single performance problems. Yeah and you should be able to just swap out the strategie, hit things with some load tester and see how many request per second you get. regards, Lukas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
