BT

InfoQ Homepage Presentations Conceptual Algorithms

Conceptual Algorithms

Bookmarks

Bio

Tom Preston-Werner is one of the founders of GitHub. He's created various Ruby tools such as the monitoring tool god, and many more.

About the conference

RubyFringe is an avant-garde conference for developers that are excited about emerging Ruby projects and technologies. They're mounting a unique and eccentric gathering of the people and projects that are driving things forward in our community.

Recorded at:

Jan 17, 2009

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Entertaining talk

    by Markus Kohler /

    • Entertaining talk

      by Markus Kohler /

      Your message is awaiting moderation. Thank you for participating in the discussion.

      It's a little bit shocking how difficult it is in Ruby to analyze memory leaks.
      Analyzing memory leaks is easy in Java (Eclipse Memory Analyzer).
      Analyzing memory usage is much more difficult, but still can be done with MAT. Check my blogs posts

    • Re: Entertaining talk

      by Werner Schuster /

      Your message is awaiting moderation. Thank you for participating in the discussion.

      I'm not so sure - the memory leak Tom's talking about is a leak in the Ruby interpreter not an application leak.
      There are a bunch of leaks - although recently a fix for many of them was found:
      www.infoq.com/news/2009/01/ruby-patches-fix-leaks
      (turns out it was naughty GCC + the conservative Ruby GC).

      For the nice kind of memory leak (the self-inflicted one in user code) Ruby doesn't need outside tools since it can look at the objects in the heap and iterate over the reachable ones. Eg here's a simple homegrown profiler using ObjectSpace:
      scottstuff.net/blog/articles/2006/08/17/memory-...

      Obviously - you'll still need some of the algorithms for analyzing the object graph and figuring out what might be a memory leak or not, and tools like MAT have these of course.

    • Wau!!!

      by Jure Srsen /

      Your message is awaiting moderation. Thank you for participating in the discussion.

      Thanks a lot for this presentation, Tom!
      I would listen to audio versions of this in a regular podcast :)
      Jure Sršen

    • Re: Entertaining talk

      by Markus Kohler /

      Your message is awaiting moderation. Thank you for participating in the discussion.

      Sure that was a leak caused by the GC not working correctly.
      I never heard of such a bug in the JVM GC within the last 9 years.

      You typically need an external tool, because if you don't have enough memory anymore you cannot use additional memory within the same process.

    • Re: Entertaining talk

      by William Louth /

      Your message is awaiting moderation. Thank you for participating in the discussion.

      Entertaining? This guy would put you to asleep with his long drawn out project promotion, language (not just ruby itself), and inability to get to the point without meandering off the course in mid-flight. I find it amazing that the lesson in this session needed to said and in such a excruciating manner. And I thought Java conferences were bad filled with the same repeating talk show (sales) hosts.

      William

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

BT

Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
Country/Zone:
State/Province/Region:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.