Does the memory grow on your project? Are you tired of using OOM killers? Spent a lot of time debugging, but didn't find a leak source? Look into an effective way to find the leak source.

1. Hunting down memory leaks
Sergey Alekseev

2. Hunting down memory leaks
Sergey Alekseev

3. What’s a memory leak?

5. Bloat vs. Leak

7. Get rid of a memory bloat first
*disable NewRelic developer_mode
in staging

9. How to hunt down a leak?
1) Find
2) Destroy

10. How to find a leak?
First look into
https://github.com/ASoftCo/leaky-
gems

11. The most effective way
Siege + New Relic + Skylight

12. /action-1 /action-2

13. New Relic – Transactions
• Most time consuming
• Slowest average response time
• Apdex most dissatisfying
• …

16. 2 types: Ruby & C memory leaks

17. Ruby memory leaks
• Errno::ENOMEM
• GC.start
• ObjectSpace.count_objects
• ObjectSpace.each_object(String)
• GC.stat

18. C memory leaks
• Valgrind
• https://lbtwiki.cern.ch/bin/view/Online/Kcach
egrind
• Heap dump

20. Сергей Алексеев
Ruby developer, Founder @ ASoft.co
• https://github.com/sergey-alekseev
• info @ asoft.co
• http://sergeyalekseev.by/#contacts