Use a delayed_job task for the long running task. This will free your mongrel process for further requests as delayed job runs as a separate ruby process but loads the rails environment. You can use "send_later" for this and this requires minimal code change.
- Gautam @gautamrege On Wed, Nov 10, 2010 at 6:06 PM, Adam <[email protected]> wrote: > Yeh i thought about mongrel cluser - I'm just imaging the discussion > with the server admins ;) > > On 10 Lis, 13:23, Michael Pavling <[email protected]> wrote: > > On 10 November 2010 12:12, Peter Hickman <[email protected]> > wrote: > > > > > How much data is being loaded? If you are adding a large amount of > > > data inside a giant commit statement then the database could become > > > inaccessible for everyone else until the load completes. > > > > Worse than that, IIRC, Mongrel serves one request at a time. If your > > request takes a long time, *nothing* else will respond while it's > > processing. > > Consider a Mongrel cluster (so there are other Mongrel instances to > > handle other requests) or better yet, switch to Passenger with Apache > > (or NGinx, etc) > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<rubyonrails-talk%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
