Hi, In my pretty easy CMS application i have written a own configuration handler, which is called very early during a request. This request fetches all cms pages from the database and adds all according routes to the routing. In this way you could use the link_to and url_for helpers as you are used to. 3000 routes, that hurts :) for this reason i split another application into smaller applications and share other code in there.
Frank Am 19.10.2009 um 22:38 schrieb Jacob Coby: > > Hi all, > > I've been working on a symfony 1.2 app that includes a CMS. > Unfortunately, the CMS system generates approximately 3000 routes > programmatically across 4 different module/actions. Unfortunately > there is no sort of pattern to the routes and the cms uses the routing > system to generate the final url. For example, cms/index?id=23 would > get translated to /about_us. And cms/subpage?id=56 would get > translated to /another_page. > > This generates a 6.5mb routing cache which expands to well over 64mb > once running in PHP (I had to set the memory limit to 128mb just to > get it running). With a small EC2 instance (256mb), the site > immediately starts to eat up the 200mb free and marches towards the > swap of death. > > I tried writing a custom routing object that would query the database > to do the routing, but it doesn't solve the problem of needing to > generate the urls from page IDs. > > Does anyone have suggestions on how to get this routing system under > control? > > Thanks, > -- > Jacob Coby > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
