Lukas Kahwe Smith wrote: > 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 would be better: Add something like ", $options = array()" to the signature OR add a new method to configure next call of forward(), e.g. setForwardOptions(array $options) ? And then provide switches like 'check_generator' => false, 'check_available' => false For example that available check should only happen once per request. >>> 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 :) Hm, is there a tool to view debug information? Or do I have to use a special editor? I installed it but I only know the nice error messages.. >> 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. Ok. There is a branch that can be used.. ;-) First step should be to create a test project for two reasons: On one hand to have something to run the benchmarking on. Maybe with some tasks to easily switch configuration settings. On the other hand the sad truth is that there are almost no unit tests for the controller - so the application could be a good test environment if changes start to happen. I would like to see changes without BC breaks. To let existing projects benefit from perfomance improvements I could imagine some more controller magic that is examing an application or a module for existing generator.yml and other stuff so the controller is able to auto tune itself. Regards, Matthias --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
