On Mon, Oct 13, 2008 at 7:13 AM, Robby Russell <[EMAIL PROTECTED]> wrote: > > On Sun, Oct 12, 2008 at 8:50 PM, Anthony Ettinger <[EMAIL PROTECTED]> wrote: >> My ISP only has 1.8.5 and Rails 2.1. >> I think there is a logic error somewhere in my code, prior to about a >> week ago, the site was functioning fine. >> >> If someone has any ideas on how to debug the 99% CPU usage, I'd be >> interested in hearing. > > Anthony, > > Are you seeing similar results when running in development? Has much > changed in the application (code or visitor-wise) in the last week or > so that could be triggering this behavior? > > You might consider looking at the performance tools from New Relic or > Five Runs, which can assist you in determining where some of the > bottlenecks in your code might be lingering. > > Good luck! >
Its very odd, I have test.example.com (test) and example.com (prod) on the same server, and the code has been deployed to both. However every time I start the prod mongrel_rails server, each request hangs and eats up CPU at 95% and takes 10 seconds for a request to complete. test.example.com does not have this problem, it serves the pages in under a second. I originally thought it may be the DB, so I made prod (example.com) use the test environment, and the issue continues. I don't know what else it could be, as they are seemingly identical when both are running as "test" environment. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
