Hi,
We'd still like to ask you to add the Redisctor app to a separate host process and select it to see its CPU utilization. Assuming that still shows high, other steps would be as follows:
- Run an application with
UWS Interactive Host. Monitor CPU usage in TaskMgr.exe. See if CPU usage when running in Interactive Host is different from when running app in a services.
- If you are a software engineer, consider attaching MS Visual Studio debugger to either the host process (it's ID is shown when host process is selected in the UWS Explorer), or to the Interactive Host - if it shows high CPU utilization too. This may show why CPU is pegged so high.
Theoretically, such high CPU usage could happen if application folder somehow gets frequently modified, causing ASP.NET to continuously recompile the app. We saw similar problems with applications that are modifying their web.config on application start, causing infinite loop of recompilation and restart. But we didn't see this kind of problem where any application runs up CPU.
Best regards,
UltiDev Team.
Please donate at
http://www.ultidev.com/products/Donate.aspx to help us improve our products.