Hi, I am a little new to the scene so i will do a short introduction; i am a php developer for a quite popular German dating website. Since 1 year now, we run symfony to deliver content to 20,000 concurent users at peak time. So we have a lot of performance problems that we try to solve and routing is one as well.
Your solution is quite interesting; in fact i am working on something very similar just this week as well and was going to publish it on our company blog until one of my workmate points me to your post. Basically i created a task to generate the rewrite rules in the htaccess based on the routing config. I am still in development, but i can see the difference so far: - no unique frontend entry point; i generate a php file based on index.php for each routing rule. - focus on other webservers; we use nginx in prod, i just used apache for debug. As they both accept PCRE rules, it shouldn't matter. At the end, my rules looks more like: RewriteRule ^moduleuno/(\d+)$ _cache_routing/module1profile.php?id=$1 [QSA,L] I find it more elegant but i guess it is my own opinion :) Anyway you seems more advanced (testing, factory...) , i guess i will leave my plugin as it is. Still i am highly interested in using this solution in production and with nginx. Do you have any plan for an nginx output? If not i can take a shot at it. Cheers, Boby On Oct 7, 4:42 pm, Thomas Rabaix <[email protected]> wrote: > Hello, > I have been working on an original concept with goal to speed up symfony > routing management : write a mod_rewrite file from the routing.yml file > > Please read > :http://trac.symfony-project.org/browser/plugins/swOptimizeRoutesPlugi... > > The current implementation is very alpha, > > - sf_method requirement is not handled. > - the plugin save 9Mb of memory on a 60Mb memory usage per request (I > have php5.3 64bits) > - the routing.yml.php is now 240Kb instead of 1Mb (400 routes) > - routes are loaded on demand, so there is only 10-30 sfRoute instance > per request > - direct access to the route (so no php route matching) > > The only problem (and not the less...) is the server handle less request > than the current implementation (sf1.2) ! It is not an issue with the > mod_rewrite file, but with the current php implementation. > > For now, I have no time to profile the implementation, but if anyone has an > idea, please share it ;) > > -- > Thomas Rabaixhttp://rabaix.net --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
