3 ms·
It really depends on your needs. My comment was in regards to the memory footprint. There was an Engineyard blog post about that recently. Basically if you do
by cschneid 17y ago
It really depends on your needs. My comment was in regards to the memory footprint. There was an Engineyard blog post about that recently. Basically if you do some non-obvious things, you can just explode out the size of ram, and because of how ruby works, it'll never get given back to the OS.
Edit: http://www.engineyard.com/blog/2009/thats-not-a-memory-leak-its-bloat/ http://www.engineyard.com/blog/2009/thats-not-a-memory-leak-...
- mikeryan 17y agoPoor use of an ORM (or pretty much any robust full-featured library) has its risks. I'm not sure how you provide features that AR includes without putting your memory at risk of overuse. Model.find(:all) is going to be problematic across the board, there will always be a risk when you start playing with things like including children (there's a great benefit as well). You need to know what you're doing with any ORM.