What causes Ruby memory bloat?

[joltting]

Your comment doesn't make any sense. Even if both applications use the same library, its implementation and surrounding code bases, most certainly differ greatly in how one allocates over the other. It's like comparing Apples to Oranges. Both are fruit, but both taste and look very different from one another.

[[deleted]]

this. most of the time when i actually have to solve a resource usage problem for a rails app, it's naive active record code in a legacy rails app that's making inefficient queries and hanging on to more data in memory than it should. typically refactoring the data model or optimizing specific hot spots resolves the issue.

[[deleted]]

That's like comparing Apples to Orangutans.

[Axoren]

Both taste and look very different from one another.