Few quick questions.
What is the risk of turning off the mutex lock? I have a particular
controller which fires off snmpwalks/gets to pull back data. It works
great if everything is up, but when I test against a hung snmp server,
I notice that lock getting in the way of other requests.
I have just ran a test with mutex turned off and it seems to work
great. But, I was wondering what the risk is of me doing that.
In addition, I am using activerecord right now, in other controllers.
Can you turn off the lock per controller? I could switch to sequel
if that made a difference, as I see a lot of reference to AR when
talking about the lock.
Or, is there a better way? I''ve just started looking briefly and see
that I can return a Proc object and let mongrel take care of that in a
thread for me, or run the render_deferred command which I''m just
guessing is doing the same thing. Would it be smarter for me to
starting looking at something in that direction?
Thanks for any insight!
Dusty Doris
