Rufo Sanchez said about 12 hours later:
Thanks for the great presentation - many of us didn't stick around as we wanted to get into the design talk before they shut the doors, but as last year your talk was filled with tons of juicy nuggets. Really good stuff.
Dan Kubb said about 19 hours later:
Ezra, I had tickets to Railsconf, but wasn't able to attend -- yours was one of the main talks I wanted to see, so thanks for putting these up.
Now that I've read through the presentation, I didn't see any mention of the Varnish HTTP proxy. I was curious if you've looked at it or not and how you think it stacks up against Nginx.
Alex said 1 day later:
Thanks for the slides. Very interesting I am sorry I did not get to hear the talk.
Out of interest, where can I find more details about the integration of Neko in to Nginx?
I know this is outside of the scope of this blog but do you have any idea why Neko has been chosen of Lua? I am not saying one should have been chosen over the other, I am just wondering what contributed to the decision.
Rufo Sanchez said 1 day later:
Ezra did mention briefly that Nginx's author believed Neko to be faster in his circumstance than Lua - not sure of any other reasons but I thought I'd mention it.
Rich Duzenbury said 3 days later:
Awesome presentation. Easily the most content of any of the others that I saw.
I'm trying to get into xen now. You made a comment during your talk that '8 way 32Gb Ram machines aren't that hard to come by'. I'm curious as to whether you are building them yourself, or do you know a good vendor?
Also, when you want to install xen, which package or method do you use? I see they have 'enterprise', 'server', 'express' and 'open source'. If open source, it seems that you need a distro loaded before you can install. Can you share what distro you prefer?
Ezra said 4 days later:
Rich- We use plain old open source xen, just now getting on Xen3.1, we roll our own gentoo for our linux. But centos or debian are easy ways to get started with Xen as they have packages for xen kernels easily available. Highly suggest getting a precompiled kernel Xen working first before you try building custom kernels. and such.
We use all supermicro hardware. getting it from silicon mechanics lately and they do a good job.
Eugueny said 5 days later:
Awesome PDF, thank you. I have 4 questions though.
1. I am wondering where is this coming from: "95% of Rails app will leak memory". I have very little experience with Rails, but my understanding is that Ruby's green threads implementation is the only "shady" area where nasty leaks can occur.
But rails is 100% single-threaded. What leaks are you talking about then?
2. My second question is about "most Rails apps are RAM bound, not CPU bound". And then you say that typical Mongrel instance eats 120MB. Meaning? Is a maximum RAM allowed per instance? And then it fails (ruby memory allocation) or what?
3. How many Mongrel instances do you recommend instantiating per CPU/Core?
4. I think I don't get your reasoning behind "Apache's bloat". Does that lead to slow performance? Is that a overall system-wide bottleneck in your deployment?
Once again, awesome presentation. Thank you!
Ezra said 25 days later:
@Fred- OpenVZ does not offer the same level of separation since all VM's run on the same kernel. THis means that VM's can have a much more drastic affect on other VM's on the same machine. In Xen each VM has its own kernel and this allows for much better separation of concerns.