dino d. wrote: > 1) how do you/can you detect and removed unused gems or modules?
Ideally you've never added anything you don't need and removed things that became deprecated. If not: do you have a test suite? Tracking code coverage or just removing things to see if tests break is a sure-fire way of knowing what's required and what's not. > 2) what kinds of things make memory bloat? can you give me a push in > the right direction based on experience? do i start in my controllers > or models, etc.? In no particular order: - Having many routes - Using gems that leak (hpricot, feed-normalizer, old versions of RMagick) - Calling AR#size instead of AR#count where applicable - Retrieving large sets of data or columns where you don't need them - Loading binary files into memory Please do add to the list. -- Roderick van Domburg http://www.nedforce.com -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en -~----------~----~----~----~------~----~------~--~---
