Fernando Perez wrote: > My munin graph show that when the rails app goes out of control, there > is a raise in the number of interrupt and context switches.
When you say 100%, do you mean the usage goes up and then bounces around, say between 95% and 100%? Or do you mean it flatlines at exactly 100%, with no bouncing? The former means an infinite loop that accesses some IO resource, such as the wire or the database. You could also have some kind of endless conversation, where event A (such as an Ajax hit) triggers event B (such as a page refresh), which triggers A again. The latter means you have a simple infinite loop that is busy doing only Ruby statements, such as "nil while true". How are your unit tests doing? Do they cover all this logic, so they might show a similar loop or dead spot? Can you "comment out" entire blocks of your app, such as entire controller actions, and then run the app and see if the problem goes away? If it does, the problem is in the last action you clobbered, so put it back in and then clobber half of it. Keep clobbering until you find the region of coding doing it. All generic techniques - no I don't know the difference here between Webrick and Passenger - but they generally can't hurt! -- Phlip --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
