hoodwink.d enhanced
RSS
2.0
XHTML
1.0

RedHanded

Oh Nice, Mongrel Gets Real Money #

by why in cult

You guys say you love Ruby, but are you really giving Ruby the elaborate gifts of cash it longs for? From zedas’ pre-release announcement for Mongrel 0.3.12:

Mongrel now has sponsorship from Eastmedia in partnership with Verisign to make Mongrel fast and stable enough for enterprise class loads (meaning “gigantic”, not “Java style”). Their sponsorship has made it possible to get large pools of test servers, payment to work on Mongrel, and a real application to use Mongrel on.

Mongrel is the hot news for Rubyists this year. A blazing little web server which finally adds some sense to Ruby on the web. Skeptical? I’d say you take a look at Zed’s Lighttpd + Mongrel tutorial and just mull it over. Think: eliminate FastCGI in favor of a proxy. You already run FastCGI as a separate process. Why not a little web server that you can fiddle with on its own?

27 Mar 2006 at 10:52 | 13 comments

jakdak

said on 27 Mar 2006 at 11:37

mongrel is just ace. im using it for dev stuff and its refreshingly fast cw Webrick. great news !! (does this make SCGI mostly redundant ?)

why

said on 27 Mar 2006 at 15:06

Yeah, you know, if you can start to look at proxying at just another protocol (like FastCGI and SCGI ) for servin up.

drbrain

said on 27 Mar 2006 at 16:18

With Apache’s mod_proxy you get a 20% performance hit. How much is lighttpd’s?

GregoryBrown

said on 27 Mar 2006 at 21:40

That sounds awesome! All of those peoples are good peoples, and you are good peoples too, why.

GregBrown

said on 27 Mar 2006 at 21:41

My name is not GregoryBrow :)

jubo

said on 28 Mar 2006 at 03:39

So far I have used mongrel standalone and it has been a rocket ship, but I don’t see the immediate advantages of proxying it instead of using fastcgi.

Zed Shaw

said on 28 Mar 2006 at 10:16

Instead of thinking, “how is this better behind my lighttpd setup”, think, “Wow, I now can put Ruby on Rails behind my company’s existing infrastructure without teaching them about spawn-fcgi.” That’s the main reason for Mongrel: speed of fastcgi with all the existing infrastructure support of HTTP . Imagine being able to just put an F5 load balancer in front of a gang of Mongrel servers and skip the whole lighttpd proxy setup. The mind boggles at the flexible simplicity.

LninYo

said on 28 Mar 2006 at 15:06

You need to explain this setup in more detail for those of us who can’t readily grasp the detailed difference between spawn and mongrel setup etc. kthxbye :)

Amiroff

said on 29 Mar 2006 at 01:23

Mongrel is really promising, I am actually planning to use it instead lighttpd in our enterprise. Just wondering though, how would it work with capistrano? Anyone has experience with capistrano/mongrel duo?

Thanks.

Zed Shaw

said on 30 Mar 2006 at 05:32

LninYo, http://mongrel.rubyforge.org/docs/lighttpd.html

Detailed docs including how to use CML to get page caching at lighttpd speeds. Memcached setup coming soon.

ozmm

said on 30 Mar 2006 at 11:46

We use Mongrel at work to serve all our internal Rails apps. It’s insane, this kid. Sometimes I think the page has loaded before I hit the return key. Thanks so much for it.

Fred

said on 30 Mar 2006 at 15:38

For rails, wouldn’t it be better with a single-threaded version of Mongrel? I can’t think of a reason why Ruby threads would be useful here…

Branstrom

said on 30 Mar 2006 at 16:57

Mongrel is Teh Shit.

Comments are closed for this entry.