Carl Lerche talks about how to write fast ruby code. Yes, ruby is scalable. Scaling != speed. Focus of this talk is on speed. Ruby is fast enough for the vast majority of use cases.
“Slow code is your fault.”
How can I write fast code?
1. Write slow code: well-structured code that is easy to read. Don’t worry about performance the first time around. You can’t tell from the beginning what matters.
2. Use the scientific method.
- Define the question
- Gather information: where is time/memory being spent?
- Form Hypothesis: why is this chunk of code slow/memory hog
- Perform an experiment and collect data
- Publish results (restart if needed)
Need questions like: “why is action X taking 600ms? ” why is 60% of a Merb dispatch cycle in content negotiation?” Why are my mongrel instances growing to 300MB of memory”
Some useful tools:
- RBench
- ruby-prof to generate profile data / kcachegrind: for reading profile data
- explain analyze log files
- New Relix / five runs
- memory_usage_logger
- Bleak_house (memory leaks)
Garbage collector is a conservative mark and sweep garbage collector. When it runs all your code stops. Each run can take 50-150ms. Triggers befre grabbing more system memory (every 8MB).
Avoid creating unecessary objects. Understand the difference between Ruby methods (e.g. the difference between reverse! and reverse).
DataMapper’s identity map is pretty awesome.
Beware of modifying large strings.
Don’t concat strings just to pretty print them across lines. Do this instead:
s = "Here is my long string"
" that continues"
Beware of closures.
No code is the fastest code. Be lazy. Don’t run code till you have to.
“Compiling your code.” Iterating is slow. Ruby’s AST is fast. (This is a little crazy, but sometimes you need it.)
Make sure you have great tests, then when you optimize you can make sure you didn’t break anything.