Bug #9800


Added by sam.saffron (Sam Saffron) over 5 years ago. Updated 5 months ago.

Target version:
ruby -v:


Many users are complaining about memory bloat in 2.1 series of Ruby

As denoted in there is an excellent plan by ko1 to address this.

In the mean time I suggest we reduce GC_HEAP_OLDOBJECT_LIMIT_FACTOR to 1.3 which effectively means that instead of memory doubling it only increases by 1.5x or so over 2.0 series.

It is great we have the setting, but the reality is that most users will not want to play with this.


1-committed_as-ruby-2.0.jpg (21.2 KB) 1-committed_as-ruby-2.0.jpg ariveira (Alexandre Riveira), 09/08/2014 10:50 PM
2-committed_as-ruby-2.1jpg (22.5 KB) 2-committed_as-ruby-2.1jpg ariveira (Alexandre Riveira), 09/08/2014 10:51 PM
3-committed_as-ruby-2.1-factor-1.3.jpg (22.6 KB) 3-committed_as-ruby-2.1-factor-1.3.jpg ariveira (Alexandre Riveira), 09/08/2014 10:51 PM


Updated by ko1 (Koichi Sasada) over 5 years ago

Sorry for late response.

I can agree this proposal because current default "2" also has no evidence to use.
I think more survey are welcome to set ideal default setting. 1.7? 1.5? 1.3?

However, already 2.1.2 released?

Updated by hsbt (Hiroshi SHIBATA) over 5 years ago

How about performance down of this change?

Updated by hsbt (Hiroshi SHIBATA) over 5 years ago

  • Status changed from Open to Feedback

Updated by bitsweat (Jeremy Daer) over 5 years ago

I'm running Ruby 2.1.2 with GC_HEAP_OLDOBJECT_LIMIT_FACTOR = 1.3 with good results, but I didn't do a thorough survey of behavior.

Does ko1 (Koichi Sasada) suggestion ( change the situation, and tuning of this parameter?

Updated by ariveira (Alexandre Riveira) about 5 years ago

The following charts 32bit linux server with 64gb 100 puma aplications and rails 2.3.11. The first chart contains ruby 2.0, the second ruby 2.1 and the third ruby 2.1 with GC_HEAP_OLDOBJECT_LIMIT_FACTOR = 1.3.

I dispose doing tests with ruby with other values ​​for GC_HEAP_OLDOBJECT_LIMIT_FACTOR as 1.2, 1.3, 1.5, etc.

Performance for me was not affected. My test is to do something like:

1.upto (100_000) do | i |
MyModel.find (i)

In parallel check if the system crashes or is slow. With ruby 2.0 is slow, even with ruby 2.1 not the 1.3 FACTOR. To perform the above test have to make the change suggested by Eric Wong at #10009.


Updated by naruse (Yui NARUSE) almost 2 years ago

  • Target version deleted (2.6)

Updated by jeremyevans0 (Jeremy Evans) 5 months ago

  • Status changed from Feedback to Closed

Also available in: Atom PDF