News for hackers. Stuff that matters.

dmitrytsepelev

Memory bloat in Ruby happens when someone loads a lot of data to the memory. Ruby Virtual Machine does not return most of the allocated memory to the operating system even after data is collected as a garbage. It’s not a big deal for local development or console programs, but if you have a bloat in the big Rails app it might cost you a lot of money.

It is quite easy to find a fix memory bloat when it happens, but can we prevent it?

Re:Why Ruby Has Symbols on Thursday April 14, 2022 @09:31AM (#31026717)
Java does use string interning for constants. It can help in any case when you have a lot of instances of the same string (and when you need to compare that strings)
Re:Why Ruby Has Symbols on Thursday April 14, 2022 @08:59AM (#31026368)
Thank you for catching that! Not sure where my eyes were, feels like it's a remnant of another version of the sentence. Removed
Re:How to GraphQL with Ruby, Rails, Active Record, and No N+1 on Tuesday November 10, 2020 @01:53AM (#25043403)
In this case the row size can become huge. Also, how to make sure it's consistent? (I mean foreign keys/unique indexes/etc)
Re:How to GraphQL with Ruby, Rails, Active Record, and No N+1 on Tuesday November 10, 2020 @01:47AM (#25043381)
Great post! By the way, the reason why ar_lazy_preload exists is that neither me nor anyone else around me heard about goldiloader at the moment when ar_lazy_preload was created