After recently updating a rather large app from 2.0.2 to 2.3.5 (running on ruby 1.8.6, latest apache and passenger) the CPU used by the ruby process would jump to 100% for a good 3 secs and locked up the server within minutes. I was able to roll back the changes easily enough, but I am now pulling out my hair trying to figure what the issue might be.
How can I figure out what it is in my large code base that has run perfectly smoothly on 2.0.2 for years, but now running on 2.3.5 causes the CPU to jump to 100% and render the app unusable? (The app runs fine and all my tests pass, it just crumbles under any load) Thanks... -- 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.
