On 29 Oct 2008, at 14:31, michael_teter wrote:

>
> Hi.
>
> I'm troubleshooting a problem, and I would love some help
> understanding what is going on.
>
> The problem is that Mongrel/Rails appears to hang or completely block
> if one of the users initiates a very slow, long-running query (via an
> ad-hoc report generation tool from within the app).
>
> For example, user A does a big query that takes minutes to complete.
> User B tries to do anything, but Rails seems completely dead.
>
> Should Rails be blocking on that query, effectively a single-user
> server?  (I certainly wouldn't expect this...)
>
Yup that's the way it is. load balancing across several mongrels helps  
a bit, but not massively because most load balancers just spread the  
load equally - they don't prioritize mongrels that aren't processing a  
request.
Rails 2.2 is thread safe, but MRI's less than stellar threading means  
that won't make a lot of difference if you are using MRI. For jruby  
things could get very interesting.

Fred
> Secondly, for what it's worth, I'm running a mongrel cluster, but that
> isn't helping right now.
>
> More info:
>
> "top" shows the host machine completely idle.
> development.log shows only user A's query SQL, but it does not show
> user B's request for a new page.
> When user A's query finally completes, then suddenly Rails comes back
> to life, and user B gets a response.
>
> This is a serious problem for me right now.  It must be a
> configuration problem, because there's no way Rails is designed to
> behave this way...?
>
> Oh also, the database is hosted on another machine, and it's Oracle 9.
>
> Thanks!
> Michael
> >


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to