RailsConf 2011: Aaron Patterson, "Double Dream Hands: So Intense!"

Channel:O'Reilly · Length:47:34 · Published:2011-05-18 · Views:25585

Watch on YouTube

Summary

Aaron Patterson's RailsConf 2011 talk on Rails 3.1 performance, showing why deeper Rack middleware stacks slow Rails and how a shallower pipeline helps. It also touches on Rack API design.

Why HN recommends it

Cited in Rails performance and Rack design discussions for Patterson's analysis of stack depth and garbage collection.

The interesting stuff happens around the 20 min. mark. — HN, 2011

Python, Ruby & scripting languages · Web development · Software performance & optimization

Subtitles (excerpt)

but uh before I begin I want to tell everybody I have a lot of love for the Ruby community and I want to say thanks to a few people first um first off I want to say thanks to John he's been doing a lot of good work on uh active record uh relation codes so you should all tweet at him and say thank you um the next person I want to say thank you to is um well not really thank you I just want to show him some love here is it doesn't look like love uh this is this is a picture of this is a picture of Michael feathers and he told me that he put my picture in one of his presentations so uh I told him all right I'm going to put a picture of you in one of my presentations so um I am going to give him a [Laughter] kiss so thank you Michael feathers uh the next thing I want to say is um I also love Jose valim a lot I tried to kiss him the other night and he was not too excited about it um so this talk is called double dream hands so intense what does it mean I I don't know uh hopefully you'll find out anyway so now I'm beginning now you can start the clock at 45 uh all right uh oh my God happy rails cof [Applause] welcome um in case you got lost you don't know where you are my name is Aaron Patterson uh you can find me on the internet is Tender Love um I work for a giant

On Hacker News

There is a talk by Aaron Patterson from RailsConf talking about why rails 3.1 is slower than rails 3 and rails 2.3. Basically the rack pipeline is getting deeper. Because rack is so simplistic every request requires you going through that pipeline and back again. His solution is to break up the pipeline into 3 separate types: generators, filters (for response data), and lifecycle hooks. Doing thi… — maercsrats, 2011-07
Nice article, Jose! For those interested, Aaron Patterson (tenderlove) talks about this in his RailsConf talk, starting at 26:45. [VIDEO] — jonsmock, 2012-06
As the number of Rack middleware pieces in a base Rails app grows, it gets slower. MRI and YARV spend a lot more time doing GC as the stack depth grows. Aaron Patterson mentioned that he was working on a modification to the Rack API where each piece of middleware did not call the next piece, reducing the stack depth and drastically improving the runtime performance of Rails apps. Here's the video… — getsat, 2011-12
In Aaron Patterson's recent "Double Dream Hands: So Intense!" presentation[0], he came to the conclusion that Rails 3's slowness is because MRI sucks at GC on a deep stack depth. The average stack depth of Rails 3 applications is ENORMOUS. He mentions in the video that he rewrote the Rack API to pass a mutated var to the next piece of middleware in the Rack chain instead of calling the next middl… — getsat, 2011-09
I don't want to be defending the OP's position, but. . . settings.py is a mess. Even Simon's written a post bashing it ( [LINK] ). I cringe a little starting up a project and having to dive into the settings.py file. In some ways, Django tries to be flexible, but it's clumsy. For example, you can have your templates in your app directories. So, you have /path/to/project/posts/templates and /path/… — mdasen, 2011-07

Related videos