get current CPU utilization in C#

Question

I want to have current CPU utilization in my project

namespace Monitoring_Tool
{
    public partial class ajaxExecute : System.Web.UI.Page
    {
        private          


        

Answer 1

It is a performance counter that heavily depends on when you read it. A processor core is either executing code, running full bore at "100%". Or it is turned off completely, stopped by the HALT instruction. The "% Processor Time" counter tells you for how many % of the time, since the last time you checked it, it has been executing code.

So you will only get meaningful values if you wait long enough between sampling it. One second is boilerplate, that's what you see in Perfmon.exe and Taskmgr.exe. The shorter the interval, the less accurate the number gets. It starts to vary wildly, jumping between 0 and 100%.

So getting 0% in the page's Load event is normal, it just initializes the counter to set the start of the interval. Getting the next sample is hardship, you can't realistically do this in the event handler. You'd have to do something drastic like having a separate timer or thread that samples at one second intervals and use that value.

Answer 2

That's because you need to call NextValue multiple times on the same PerformanceCounter instance (so at least twice). The first call will always return 0.

You can work around this (sort of) by calling NextValue twice in your Page_Load event handler, only storing the return value of the second call:

        float cpuUsage = 0.00F;

        this.theCPUCounter.NextValue();
        cpuUsage = this.theCPUCounter.NextValue();

The reason it shows in the QuickWatch of the debugger is probably just because it is (implicitly) called multiple times (once by the program and once by the debugger for the QuickWatch value).

Update to the "sort of" above:

As others have mentioned you usually need to sleep some time between the two calls to actually observe a difference in CPU load that results in a "measurable" difference. Sleeping for 1 s usually does the trick, but might not be an acceptable delay in the loading of your page.

What you really want to do is provide a background thread that repeatedly queries this performance counter, sleeping a couple of seconds in between. And storing the result somewhere. From your Page_Load or other events / functions query the (last) value. All with necessary locking against data races of course. It will be as accurate as you can get with regards to this pointer.

Since you are obviously using ASP.NET you have to be careful with such background threads. I'm no ASP.NET expert, but according to this it should be possible, even though the thread (and the perf counter readings it did) will be recycled, when your app domain / web application is. However, for this kind of functionality that shouldn't be an issue.