4 messages in ru.sysoev.nginxRe: Rails Spawn plugin under nginx
FromSent OnAttachments
Tr SchneitMar 30, 2008 12:25 pm 
Corey DonohoeMar 30, 2008 12:43 pm 
Tr SchneitMar 30, 2008 1:38 pm 
Tom AndersonOct 13, 2008 2:59 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: Rails Spawn plugin under nginxActions...
From:Corey Donohoe (atmo@public.gmane.org)
Date:Mar 30, 2008 12:43:10 pm
List:ru.sysoev.nginx

Hey,

Every client we have using spawn at engine yard has problems. The short answer is just don't do it. You need to use real queueing a la bj, backgroundrb, starling, etc. I'm pretty sure that the upstream gets confused with all the fd closing/reopening/reconnecting.

__ Corey Donohoe cdonohoe-NLltGlunAUd/unjJ@public.gmane.org (866) 518-9273 x207

On Mar 30, 2008, at 1:25 PM, Tr Schneit
<list@public.gmane.org> wrote:

Howdy folks - I am having trouble with the 'Spawn' plugin, which is used to launch long-running processes in the background.

When I hit a single mongrel process, it works great. However, when I hit it through nginx, a the long-running task stays within the same process. I have no clue why this is happening, but it is dragging down my performance.

Does anyone have any input?

Thanks!

-- Posted via http://www.ruby-forum.com/.