Building a More Efficient Ruby Interpreter.md

Building a More Efficient Ruby Interpreter

• 3:46

  • each Rails process is actually single-threaded and handle one concurrent request, if use thread-safe we could really run multiple threads in a single Rails process
  • memory usages increases linearly with each process

• 5:30 fork and copy-on-write

  • child process will still share most it memory with parent and only add another memory page for the value changed

• 5:50 how perl work

• 7:16 how ruby work, simple mark and sweep

• 19:00 About thread, I could not follow, I don't understand WTF T_T

References

• malloc
  • http://www.wretch.cc/blog/pinkmoon04/4107348
  • http://caterpillar.onlyfun.net/Gossip/CGossip/MallocFree.html
  • http://baike.baidu.com/view/1213621.htm
• gc

  • http://www.web-l.nl/posts/15-tuning-ruby-s-garbage-collector-with-rvm-and-passenger

    the Ruby Garbage Collector (GC) locks your application when it decides to run, which usually happens when you allocate a lot of objects.

    • delay the GC run until after the request is processed.
    • Tuning the GC

  • http://patshaughnessy.net/2012/3/23/why-you-should-be-excited-about-garbage-collection-in-ruby-2-0

  • Bitmap Marking GC for Ruby Improves Memory Usage

  • Ruby 1.9.3 Preview 1 Released, Improves GC Pauses With Lazy Sweep GC

  • Ruby’s GC Configuration

  • Playin' with the Ruby GC

  • ruby gc tuning