Comments on: Introducing Phat, an Asynchronous Rails app

By: Database Month Coming Up! « Montreal.rb

Database Month Coming Up! « Montreal.rb — Mon, 31 Jan 2011 14:28:24 +0000

[...] about the asynchronous gems? There was a big hoopla about mysql2 a while back. Is this still alive? Is it any [...]

By: Co nowego w świecie Ruby’ego #4

Co nowego w świecie Ruby’ego #4 — Wed, 21 Jul 2010 20:03:10 +0000

[...] koncepcja i zaskakująco sprawne działanie. Jeden proces Thin’a, Fibers z Ruby 1.9 i skalowanie jak ta lala Znalezione przez forum [...]

By: Особое программирование » Post Topic » Ruby 1.9 Fibers + EventMachine for Big Ruby Webapp Performance Gains

Mon, 14 Jun 2010 19:56:04 +0000

[...] in April, Mike Perham introduced Phat, an asynchronous Rails 2.3.5 app running on Ruby 1.9 and supporting “many concurrent requests [...]

By: Ruby 1.9 Fibers + EventMachine for Big Ruby Webapp Performance Gains

Ruby 1.9 Fibers + EventMachine for Big Ruby Webapp Performance Gains — Mon, 14 Jun 2010 06:10:12 +0000

[...] in April, Mike Perham introduced Phat, an asynchronous Rails 2.3.5 app running on Ruby 1.9 and supporting "many concurrent requests in a [...]

By: Losty Otaku

Losty Otaku — Fri, 28 May 2010 11:45:46 +0000

@Mike, Love the app, watched the presentation (didn’t like when that guy compared lovely open source ruby to windows). Anyway, I’m wondering what the differences between rack-fiber_pool and neverblock or is neverblock essentially the same thing minus the em_memcache?

@Gonçalo Silva, Juggernaut uses event machine to queue its messages, and runs in a separate process – so I’d say it doesn’t really need any modification.

By: Gonçalo Silva

Gonçalo Silva — Fri, 14 May 2010 00:00:34 +0000

> Everything that does network access ideally should be modified to be Fiber-aware.

Hey Mike,

Does this include gems like juggernaut, which does network access but it can be done locally?

By: Steven

Steven — Mon, 26 Apr 2010 15:00:41 +0000

Hi Mike,
great work you did here. This makes me more excited than Rails3!

I have some problems with configuring postgresql when trying to re-run the ab benchmarks. I always get the error “sorry, too many clients already”. could you show your postgresql.conf in a gist or via a commit in the phat repo? That would be really appreciated…

By: Mike Perham

Mike Perham — Fri, 16 Apr 2010 14:24:30 +0000

Yes, EM must be started since we are using it to manage the asynchronous I/O. My first thought is that we really don’t need async for rake tasks and therefore the em-mysqlplus driver should work synchronously if EM.reactor_running? == false.

There’s many hacks you can do to solve this issue but no clean solution yet.

By: Saimon Moore

Saimon Moore — Fri, 16 Apr 2010 14:01:11 +0000

Hi Mike,

I’ve been trying to use llya’s em-mysqlplus + your fiber connection pool to get a simple rails 3 app up and running. After a bit of tweaking I think I’m almost there.

I’m trying to run rake db:migrate but it’s complaining that eventmachine isn’t initialized.

So does this mean that I have to somehow initialize eventmachine when not running inside thin (i.e. in a script)?

Any help would be appreciated…

Thanks,

Saimon

By: Non-blocking ActiveRecord & Rails - igvita.com

Non-blocking ActiveRecord & Rails - igvita.com — Thu, 15 Apr 2010 20:39:57 +0000

[...] one, and finally, we need to disable the built in Mutex (hap tip to Mike Perham for doing all the dirty work for us). Now let's give it a [...]