Skip to content
0:00 / 0:00

#twitter#rubyonrails#solaris

Twitter Space 4/25/2022 -- Fail Whaling

Oxide Computer Company

8.1K subscribers • 3 videos on Hallway

YouTube

Advanced. Deep dive for people who know the field.

1.9K views4 years ago1 recommendation

Distributed systemsHistory and cultureScaling and large-scale architectureHistory of computingRuby

Jason Hoffman and the Oxide team discuss the early scalability challenges of Twitter, including Ruby on Rails performance issues on Joyent.

Context: twitter.com/ahl/status/1517869292238213120 Notes: github.com/oxidecomputer/twitter-spaces/blob/master/2022_04_… Special thanks to Jason Hoffman for joining us!

Why it's here

1 person recommends this

What people say. Recommended for its fascinating historical war stories about early Twitter scaling challenges and Ruby on Rails performance bottlenecks.

u/keloidoscopein r/programming • Recommends

On “Ruby might be faster than you think”

Some great stories about Twitter scalability were told on the Oxide and Friends podcast, featuring core Solaris engineers and the co-founder of Twitter's then cloud host, Joyent. There is one story about Twitter taking 100ms of CPU to serve a request, because Rails was using an exception to exit from a loop that was in code executing 434 stack frames deep, and the profiling showed huge amounts of time spent in bcopy, grabbing all those stack frames as part of exception handling to simply... exit a loop. Whole thing is gold but skip to 25:20 for that specific story: link to this video

u/keloidoscopein r/programming • Recommends

On “How we saved 100 terabytes of memory by optimizing 1.1.1.1’s DNS cache”

Oxide and Friends hosted Jason Hoffmann, who used to provide hosting for Twitter in the early days, and he had some classic war stories of how early Twitter got to learn some hard lessons about scaling, and why Ruby exceptions weren't a great control structure choice for hot code paths, especially combined with a deep call stack... link to this video