Skip to content
This repository
Browse code

modified: Message-in-a-bottle.md

  • Loading branch information...
commit a3c9a41ee906a5555137f06ddd19110d817a5752 1 parent aa5d43d
Ben Oakes benjaminoakes authored

Showing 1 changed file with 7 additions and 0 deletions. Show diff stats Hide diff stats

  1. +7 0 Message-in-a-bottle.md
7 Message-in-a-bottle.md
Source Rendered
... ... @@ -1,3 +1,8 @@
  1 +Synopsis
  2 +--------
  3 +
  4 +> What does really happen when we call a method? How do the different Ruby implementations actually figure out what code to execute? What plumbing is going on under the hood to get a speedy dispatch? In this talk we will have a look at the internals of the four major Ruby implementations - 1.8, 1.9, JRuby and Rubinius, focusing on their dispatch. From look-up tables and call site caches, to inlining and what on earth is invokedynamic? Expect C, C++, Java, and, of course, Ruby code. But fear not, all will be explained!
  5 +
1 6 Intro
2 7 -----
3 8
@@ -59,3 +64,5 @@ Takeaways
59 64 * Fewer instructions == better
60 65 * MRI -- what could it do better? It's adding super-instructions
61 66 * Late binding
  67 +* Symbols aren't garbage collected. You have user generated symbols? They'll take up more and more memory!
  68 + * They're the same object between instances

0 comments on commit a3c9a41

Please sign in to comment.
Something went wrong with that request. Please try again.