This project is read-only.

How to troubleshoot Orchard pegging the CPU

Topics: Administration, Troubleshooting
Jul 25, 2014 at 4:40 PM
Edited Jul 25, 2014 at 4:41 PM
I need some advice on how to troubleshoot a situation in which Orchard pegs the cpu for extended periods of time. It only happens in our production environment so attaching to the process is a last ditch effort.

I know it's Orchard because its the w3wp process and orchard is the only site we have running on the particular box.

The only hint i have as to the problem is that one time when it was happening, I happened to be in the middle of some content changes. After saving and publishing my changes, I killed the w3wp process. CPU went back down to the normal 2-5%. When I got back into Orchard, my content changes had been blown away (actually reverted back to the previous versions). I suspect is one of the 3rd party modules I've installed, but have no idea how or where to start troubleshooting.

Anybody have any ideas?
Jul 25, 2014 at 5:09 PM
First thing I would do in such a situation is to enable DEBUG logging in Log4net.config and see if anything obvious stands out in the log while Orchard is hogging the CPU.