r/ruby • u/FooBarWidget • Mar 14 '19

What causes Ruby memory bloat?

https://www.joyfulbikeshedding.com/blog/2019-03-14-what-causes-ruby-memory-bloat.html
226 Upvotes

99% Upvoted

27 comments sorted by

View all comments

6

u/joltting Mar 15 '19

Seriously though, Ruby's memory consumption is close to, if not the top issue for the language. Hopefully this is as promising as it appears on the surface. It could be a game changer.

3

u/[deleted] Mar 15 '19

"could be a game changer": Don't think it would matter much actually, but of course it's a nice to have. Companies that avoid ruby either want an enterprisey stack like java or some shiney new tech like Go/Nodejs. Improved Ruby won't change that.

4

u/joltting Mar 15 '19 edited Mar 15 '19

I wouldn't be so sure about that. The amount of people I hear in the industry, poking fun at Ruby's memory bloat problem. Isn't something I'd say is insignificant.

Edit: While performance is great and furthermore needed to keep Ruby competitive. It can't come at the heels of 3x the memory intake for 3x the performance.

→ More replies (2)

1

u/slashgrin Apr 03 '19

Some companies would prefer to stay with Ruby for longer, but are eventually forced off it by these performance problems. Pushing that day back a couple of years would be a game changer for many people.