Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Ruby 2.2 Support? #11
After I upgraded my Rails(4.1.8) to Ruby 2.2.0. I notice some error messages in my logs:
I was wondering do we still suppose to use it on Ruby 2.2? Or it should only be used on Ruby 2.1?
added a commit
Mar 21, 2015
The answer to "is there a benefit" is... wait for it... workload dependent. Tada! What a shocker!
RIncGC behaves differently from a web-request-based "Out-of-band GC", so you can't replace one with the other and expect the exact same performance behaviour.
If your app spawns a lot of temp vars and triggers multiple GC runs during every request, and you'd like to have a clean slate before every new request (and avoid triggering as many GC during requests--remember, RIncGC still slows your app down, they just won't block for the entire duration of a GC run), then OOBGC can still be helpful. If, on the other hand, you've kept your app pretty light and there isn't a lot of garbage created per request, and a GC is only triggered once every few requests, then OOBGC will actually hurt you (very slightly) than give any benefits.
However, these are broad stroke assumptions! You MUST profile your specific app!
Where assumption and reality diverge is where you'll have performance issues.