Comments on: That’s Not a Memory Leak, It’s Bloat

By: Server slower for each successive request - Admins Goodies

Server slower for each successive request - Admins Goodies — Tue, 16 Aug 2011 13:13:29 +0000

[...] Memory bloat the second suspect: http://www.engineyard.com/blog/2009/thats-not-a-memory-leak-its-bloat/ [...]

By: Tuning the Garbage Collector with Ruby 1.9.2 | Engine Yard Ruby on Rails Blog

Fri, 22 Jul 2011 17:57:32 +0000

[...] overall bloat and create more objects than you really need. Sudara Williams’s post That’s Not a Memory Leak, It’s Bloat explains the symptoms and common use cases quite [...]

By: Prodis

Prodis — Fri, 17 Dec 2010 11:03:12 +0000

"SELECT * FROM…" SQL generated by ActiveRecord is already a bloat.
For me makes sense "SELECT column1, column2, columnN FROM…" instead of.

By: Jensebraten

Jensebraten — Fri, 29 Jan 2010 19:38:31 +0000

@paul
why not has_finder ;)
named_scope :ids, :select => 'id'
works fine for me with a geodata-set ~650k

By: Ben Fyvie

Ben Fyvie — Thu, 10 Dec 2009 16:16:16 +0000

You would want to do a find on Posts that does a join to Users to do your condition. For example:
@posts = Post.find(:all, :joins => :user, :conditions => "users.activated = true")

By: Aaron

Aaron — Wed, 25 Nov 2009 23:47:18 +0000

For what its worth regarding profiling tools, the statement "Run these tools in production mode on production data " is not particularly good advice. While these tools are "… built to be non-obtrusive." they aren't as non-obtrusive as they might seem by looking at the code.

We were running with MemoryLogic/memory-usage-logger in production for a long while, having performance problems under even moderate load, and struggle to tune everything. Eventually, on a lark, we removed the memory-usage-logger and our page render time averages plummeted from 600ms down to 180ms. Adding back in the memory-usage-logger and our page render times go right back up. While this is a great tool, it adds way too much overhead to leave in a production environment.

By: foz

foz — Wed, 25 Nov 2009 14:43:04 +0000

Whoops that link should have been: http://www.fozworks.com/2009/11/25/a-really-simpl...

By: foz

foz — Wed, 25 Nov 2009 14:40:57 +0000

I discovered that another way to fight bloat is to fork (or thread, or queue) the bloat-inducing code. I've written up a blog post about my experiences: http://www.fozworks.com/admin/articles/6009

By: sensei

sensei — Tue, 17 Nov 2009 13:51:06 +0000

Actually User.find returns an association proxy, which isn't quite the same as an array. it can respond to association methods such as "posts" here.

By: Ikin

Ikin — Fri, 23 Oct 2009 00:49:10 +0000

Thanks Sudara for this superb post!
Although can you explain more about this statement:
"Ruby is greedy with memory—it doesn’t hand the memory back to the OS after the request"

Do you mean if the request allocate some memory for a variable, that memory is not released after the request? That means the process size will just keep going bigger?
Thx!