I know about GC.enable/disable
, but is there any way of controlling the Ruby 1.9 garbage collector in more detail?
When profiling my code
Yep, for short.
At first, basic constants, defining GC behavior (defaults value are shown) :
More details about GC, may help
A story from 37signals guys, which may definitively help you. They used manual GC calls (GC.start) on time, instead of memory size, and got huge boost.