Comments on: Ruby EventMachine - The Speed Demon http://www.igvita.com/2008/05/27/ruby-eventmachine-the-speed-demon/ A goal is a dream with a deadline. Sun, 14 Mar 2010 14:07:05 +0000 http://wordpress.org/?v=2.7.1 hourly 1 By: Ilya Grigorik http://www.igvita.com/2008/05/27/ruby-eventmachine-the-speed-demon/comment-page-1/#comment-212661 Ilya Grigorik Mon, 14 Sep 2009 13:23:02 +0000 http://www.igvita.com/2008/05/27/ruby-eventmachine-the-speed-demon/#comment-212661 Purab, you can use the "thin" webserver to serve Rails, instead of mongrel or phusion passenger. That's the best way to get the benefits of Eventmachine with Rails (there are downsides as well). Look into "async-thin" as well. The code above is better suited for standalone applications. Purab, you can use the “thin” webserver to serve Rails, instead of mongrel or phusion passenger. That’s the best way to get the benefits of Eventmachine with Rails (there are downsides as well). Look into “async-thin” as well.

The code above is better suited for standalone applications.

]]> By: purab kharat http://www.igvita.com/2008/05/27/ruby-eventmachine-the-speed-demon/comment-page-1/#comment-212628 purab kharat Mon, 14 Sep 2009 09:53:57 +0000 http://www.igvita.com/2008/05/27/ruby-eventmachine-the-speed-demon/#comment-212628 Where to add this code in rails project...first tell where to put these files in rails project. Where to add this code in rails project…first tell where to put these files in rails project.

]]> By: Fibers & Cooperative Scheduling in Ruby - igvita.com http://www.igvita.com/2008/05/27/ruby-eventmachine-the-speed-demon/comment-page-1/#comment-193392 Fibers & Cooperative Scheduling in Ruby - igvita.com Wed, 13 May 2009 17:43:59 +0000 http://www.igvita.com/2008/05/27/ruby-eventmachine-the-speed-demon/#comment-193392 [...] and asynchronous programming models are great candidates for application of Fibers. Ruby EventMachine allows us to asynchronously defer blocks of code to be executed when the resource (socket, file [...] [...] and asynchronous programming models are great candidates for application of Fibers. Ruby EventMachine allows us to asynchronously defer blocks of code to be executed when the resource (socket, file [...]

]]> By: Markus Jais on software development » 9 websites about Ruby/EventMachine http://www.igvita.com/2008/05/27/ruby-eventmachine-the-speed-demon/comment-page-1/#comment-158915 Markus Jais on software development » 9 websites about Ruby/EventMachine Fri, 09 Jan 2009 21:36:53 +0000 http://www.igvita.com/2008/05/27/ruby-eventmachine-the-speed-demon/#comment-158915 [...] Ruby EventMachine - The speed demon. A very good introduction to EventMachine. [...] [...] Ruby EventMachine - The speed demon. A very good introduction to EventMachine. [...]

]]> By: Tin’s Blog » [转载］Ruby的并发的一些基本限制 http://www.igvita.com/2008/05/27/ruby-eventmachine-the-speed-demon/comment-page-1/#comment-149431 Tin’s Blog » [转载］Ruby的并发的一些基本限制 Sat, 29 Nov 2008 08:28:43 +0000 http://www.igvita.com/2008/05/27/ruby-eventmachine-the-speed-demon/#comment-149431 [...] is powered by a cluster of app servers (Mongrel, Ebb, Thin), and alternative strategies like EventMachine, and Revactor (equivalents of Twisted in Python) are gaining ground as a simple way to defer [...] [...] is powered by a cluster of app servers (Mongrel, Ebb, Thin), and alternative strategies like EventMachine, and Revactor (equivalents of Twisted in Python) are gaining ground as a simple way to defer [...]

]]> By: Concurrency is a Myth in Ruby - igvita.com http://www.igvita.com/2008/05/27/ruby-eventmachine-the-speed-demon/comment-page-1/#comment-145930 Concurrency is a Myth in Ruby - igvita.com Thu, 13 Nov 2008 17:16:39 +0000 http://www.igvita.com/2008/05/27/ruby-eventmachine-the-speed-demon/#comment-145930 [...] is powered by a cluster of app servers (Mongrel, Ebb, Thin), and alternative strategies like EventMachine, and Revactor (equivalents of Twisted in Python) are gaining ground as a simple way to defer and [...] [...] is powered by a cluster of app servers (Mongrel, Ebb, Thin), and alternative strategies like EventMachine, and Revactor (equivalents of Twisted in Python) are gaining ground as a simple way to defer and [...]

]]> By: Asynchronous DB: DBSlayer & HTTP - igvita.com http://www.igvita.com/2008/05/27/ruby-eventmachine-the-speed-demon/comment-page-1/#comment-110345 Asynchronous DB: DBSlayer & HTTP - igvita.com Mon, 11 Aug 2008 16:12:04 +0000 http://www.igvita.com/2008/05/27/ruby-eventmachine-the-speed-demon/#comment-110345 [...] to easily turn any HTTP request into a non-blocking request! Borrowing some sample code from my previous post on Ruby EventMachine, we have an easy Ruby web-server (port 8082) which makes an asynchronous DB call to fetch the [...] [...] to easily turn any HTTP request into a non-blocking request! Borrowing some sample code from my previous post on Ruby EventMachine, we have an easy Ruby web-server (port 8082) which makes an asynchronous DB call to fetch the [...]

]]> By: Ilya Grigorik http://www.igvita.com/2008/05/27/ruby-eventmachine-the-speed-demon/comment-page-1/#comment-104022 Ilya Grigorik Mon, 16 Jun 2008 00:37:12 +0000 http://www.igvita.com/2008/05/27/ruby-eventmachine-the-speed-demon/#comment-104022 Jens, that's a great point. As odd as it sounds: it's so refreshing to work in a shared nothing state of mind! Jens, that’s a great point. As odd as it sounds: it’s so refreshing to work in a shared nothing state of mind!

]]> By: Jens Alfke http://www.igvita.com/2008/05/27/ruby-eventmachine-the-speed-demon/comment-page-1/#comment-103928 Jens Alfke Tue, 10 Jun 2008 14:49:36 +0000 http://www.igvita.com/2008/05/27/ruby-eventmachine-the-speed-demon/#comment-103928 This all sounds very familiar to me, as it's the way the Mac OS X frameworks (CFNetwork and Cocoa) operate. Nice to see this approach being used elsewhere! One other advantage you didn't point out is that, by avoiding multithreading where possible, you can leave your code simpler and easier to read (and debug!) since it doesn't have to deal with deadlocks or race conditions. I've written lots of networked Cocoa code and almost never had to deal with thread synchronization or locking, thank god. This all sounds very familiar to me, as it’s the way the Mac OS X frameworks (CFNetwork and Cocoa) operate. Nice to see this approach being used elsewhere!

One other advantage you didn’t point out is that, by avoiding multithreading where possible, you can leave your code simpler and easier to read (and debug!) since it doesn’t have to deal with deadlocks or race conditions. I’ve written lots of networked Cocoa code and almost never had to deal with thread synchronization or locking, thank god.

]]> By: Ilya Grigorik http://www.igvita.com/2008/05/27/ruby-eventmachine-the-speed-demon/comment-page-1/#comment-103828 Ilya Grigorik Fri, 06 Jun 2008 12:13:41 +0000 http://www.igvita.com/2008/05/27/ruby-eventmachine-the-speed-demon/#comment-103828 Jan, good point, here are the results: <blockquote> Concurrency Level: 20 Time taken for tests: 4.61886 seconds Complete requests: 40 </blockquote> Jan, good point, here are the results:

Concurrency Level: 20
Time taken for tests: 4.61886 seconds
Complete requests: 40

]]>