> > 3) don't regenerate query plans every time [cache them if possible]. > > > 5) Avoid re-generating sql escaped copies of each column name for > > tables. Cache the sql escaped column names. > > > 6) LRU cache all sql-escaped data [?] > > I attempted this 2-3 years ago with my work on prepared statements for > ActiveRecord. I did not measure any performance gains.
I wonder if tying it in with "real" prepared statements would help. Did they? > > 4) avoid n^2 filter searches as you handle a request [I believe that's > > what it does currently]. At least with the before and after filters, > > you could calculate them all once, at the beginning of the request. > > Hm, I always thought the application of filters is O(n) and not O > (n^2). :) Why would it be O(n^2)? Hmm...perhaps what I was remembering was that it was recalculating the filters per action once per request [?] Sorry it's been awhile :) -=r --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
