Ruby Performance Optimization Why Ruby Is Slow And How To Fix It(1st Edition)

Book details

Book Price $0 : You Don't Have To Accept Slow Ruby Or Rails Performance. In This Comprehensive Guide To Ruby Optimization, You'll Learn How To Write Faster Ruby Code--but That's Just The Beginning. See Exactly What Makes Ruby And Rails Code Slow, And How To Fix It. Alex Dymo Will Guide You Through Perils Of Memory And CPU Optimization, Profiling, Measuring, Performance Testing, Garbage Collection, And Tuning. You'll Find That All Those "hard" Things Aren't So Difficult After All, And Your Code Will Run Orders Of Magnitude Faster. This Is The First Book Ever That Consolidates All The Ruby Performance Optimization Advice In One Place. It's Your Comprehensive Guide To Memory Optimization, CPU Optimization, Garbage Collector Tuning, Profiling, Measurements, Performance Testing, And More. You'll Go From Performance Rookie To Expert. First, You'll Learn The Best Practices For Writing Ruby Code That's Easy Not Only On The CPU, But Also On Memory, And That Doesn't Trigger The Dreaded Garbage Collector. You'll Find Out That Garbage Collection Accounts For 80% Of Slowdowns, And Often Takes More Than 50% Of Your Program's Execution Time. And You'll Discover The Bottlenecks In Rails Code And Learn How Selective Attribute Loading And Preloading Can Mitigate The Performance Costs Of ActiveRecord. As You Advance To Ruby Performance Expert, You'll Learn How Profile Your Code, How To Make Sense Out Of Profiler Reports, And How To Make Optimization Decisions Based On Them. You'll Make Sure Slow Code Doesn't Creep Back Into Your Ruby Application By Writing Performance Tests, And You'll Learn The Right Way To Benchmark Ruby. And Finally, You'll Dive Into The Ruby Interpreter Internals To Really Understand Why Garbage Collection Makes Ruby So Slow, And How You Can Tune It Up. What You Need: Some Version Of Ruby. The Advice From This Book Applies To All Modern Ruby Versions From 1.9 To 2.2. 80% Of The Material Will Also Be Useful For Legacy Ruby 1.8 Users, And There Is 1.8-specific Advice As Well. See more