Posted by Steve on December 03, 2010
|
Comments|Read full article
A client's CMS application was hogging up to 1.2gb RAM for the passenger ruby processes, we set to work on putting the big fella on a diet and with the help of the ruby profiler, some very useful tips on finding active record bloat and the wonderful oink gem we achieved a huge performance boost and reduced resource usage.