Like most of the Ruby community, we were pretty excited by the move to generational garbage collection in Ruby 2.1. The new approach promised for shorter GC pauses and better overall performance, and for most of us, it seems to be living up to that promise. But there are still some serious flaws with the way that memory is managed in Ruby, and you should be aware of these flaws if you’re running a
![Ruby Garbage Collection: Still Not Ready for Production - The Omniref Blog](https://cdn-ak-scissors.b.st-hatena.com/image/square/f7b2c7ceca42da828599a9839ac834c9877a6f51/height=288;version=1;width=512/http%3A%2F%2Fwww.omniref.com%2Fblog%2Fimages%2Funicorn_memory.png)