Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Monitor CPU & Ram over time


05 Aug 2010   #1

Windows 7 Ultimate 64 bit
 
 
Monitor CPU & Ram over time

I'm trying to figure out how to monitor my cpu & ram over a few hours while I'm palying games , and then be able to go back later and look to see what the results were.

Any idea of how to do this in win 7?

My System SpecsSystem Spec
.

05 Aug 2010   #2

Windows 8.1 Pro (x64)
 
 

Performance Monitor
My System SpecsSystem Spec
05 Aug 2010   #3

Windows 7 Ultimate 64 bit
 
 

Yes I have that open but I can't figure out which counters to use , theres about 542 different counters for processors , but not a single one that tells me how much is being used. Same with the Memory , it has all sorts of settings except how much ram is being used.
My System SpecsSystem Spec
.


05 Aug 2010   #4

Windows 7 Ultimate (x64)
 
 

You could use Rainmeter or Samurize to have the information you want on your desktop. For example, I attach a screenshot of the meters I use - memory usage among them. The Customization part of these Forums is full of threads about the two tools, you can find all the help you might need. There is some learning curve, but once you set it up, it works great.


Attached Images
 
My System SpecsSystem Spec
05 Aug 2010   #5

Windows Server 2008 R2
 
 

If you're talking about system load, there is a way to get an approximate, general idea of how much memory (actual, committed virtual address pages) your system is using via perfmon and a Data Collector Set, and also get an idea of CPU usage over this time as well (I'll focus on memory usage, because CPU usage isn't really as important as it may first seem). Again, it's going to be an estimate, but it's a pretty good, close estimate to what your usage patterns mean in terms of physical RAM or RAM + paging file usage (you can use this to determine if you need a paging file or not as well).

In perfmon as a User Defined Data Collector Set (start > run > perfmon > Data Collector Sets > User Defined > Action > New > Data Collector Set > Create manually (advanced) > Performance Counter), you can add the "Working Set" counter under the "Process" object, and select the "_Total" instance. Then, add the "Cache Bytes", "Pool Nonpaged Bytes", Pool Paged Bytes, and "Available Bytes" counters under the "Memory" object. These give you:
  • Working Set - Gives you the amount of memory pages that have been used recently by running processes, and as such are almost all going to have been mapped into physical RAM. This number will be larger than the actual total process memory utilization due to shared pages between processes being counted multiple times as a process working set.
  • Cache Bytes - This number gives you a real-time display of the value of the system cache, the system driver resident bytes, the system code resident bytes, and the kernel paged pool bytes that are cached in RAM.
  • Pool Nonpaged Bytes - This counter gives you the amount of the kernel nonpaged pool resource size - this pool is ALWAYS mapped into RAM (thus nonpaged pool, and cannot be paged out to a paging file).
  • Pool Paged Bytes - This counter gives you the amount of the kernel paged pool resource size - this pool contains memory data that can be written to disk (in the paging file) if necessary, but is usually stored in RAM until the memory manager determines it needs physical RAM pages (when the system RAM gets full/busy/etc).
  • Available Bytes - This gives you the amount of physical RAM available for system use, and is equal to the total amount of memory assigned to the standby (cached), free, and zero page lists (I won't explain them here, it's too deep for this discussion - Windows Internals is good for a deep dive on these if you really want to learn more).

Next, add the "% Privileged Time", "% Processor Time", and "% User Time" counters under the "Process" object, and select the "_Total" instance. Then, add the "% DPC Time", "DPC Rate", and "Interrupts/sec" counters under the "Processor" object, and select the "<All instances>" instance. These give you:
  • % Privileged Time - This is the percentage of time that a process had threads executing code in privileged (kernel) mode. Since calls to privileged mode require context switching, too much privileged time can mean lower performance of a process or system depending on the data the thread is accessing, although some privileged time is normal.
  • % Processor Time - This number is the percentage of time all of the threads in a process were executing code on the CPU. This one is pretty self-explanatory.
  • % User Time - This is the percentage of time that a process had threads executing code in non-privileged (user) mode, meaning this percentage contains only application code that runs outside the kernel.
  • % DPC Time - This is the percentage of time that the CPU spent working on deferred procedure calls (DPC), which are interrupts in a system that don't run at as high a priority as a standard system-level interrupt, usually at DPC level 2. A system that does a lot of DPC processing, however, would indicate that the system is performing poorly and may be doing more than it's CPUs can handle. There's no hard-and-fast rule for this counter, but it's something you can monitor over time as you do more and more work with your computer to determine if your system is keeping up or not with the demands of the drivers on the system.
  • DPC Rate - This counter gives you an idea of the numbers of DPCs that were added to the CPU's DPC queue as each processor timer ticks on the CPU clock. This number, coupled with the % DPC Time counter, can give you an idea of how fast your CPU is processing DPCs, and give you an idea if your system is keeping up with the load generated by driver calls and other system-level interrupts - if the % DPC Time stays fairly constant but the DPC rate increases regularly, you will know your system is just too busy to keep up with what it's doing, for example.
  • Interrupts/sec - Interrupts/sec is the average rate (per second) that the processor handled hardware interrupts (not DPC interrupts). This gives an estimate of the activity of devices on the system that are generating interrupts, such as the system clock, mouse, disk, NICs, etc. Normal thread execution is suspended when the CPU is handling a hardware interrupt, so a machine with a high volume of interrupts would likely perform poorly. Again, as with the DPC counters, there's no hard-and-fast rule for this counter, but you monitor this over time as well to see if the system's devices are causing performance issues or not.

Now, spend a decent amount of time doing the things you'd normally do, and then go back into perfmon and stop/review your Data Collector log. Specifically, add up the averages and high-water marks for the 5 memory counters (they're all in bytes, keep that in mind - not MB or GB, but bytes), and you have an approximation of the actual virtual address footprint of your machine. To a very close approximation, you'll know how much virtual address pages your system uses, and in general, to where the pages are going. If this number is always less than the amount of physical RAM (in bytes) installed on your machine, you don't need a paging file (unless you run apps that explicitly don't run without one, and those are rare). If the number is ever close (and you'll have to determine what level of "close" you want to abide, if this is the case), you're going to want at least a smaller paging file, and if your usage patterns show numbers that are always way over the amount of physical RAM with your perfmon results, obviously, you need a paging file. You can also go back and look at the CPU usage patterns over this same time using those 6 CPU counters, to get an idea of what types of usage patterns you use, and if your CPU is keeping up with system demands (or if you're not using all of your CPU effectively as well ). You can use these numbers to determine if your system is adequate for your usage needs, or if you need an upgrade (or, of course, if you have a system that's overkill for what you need it to do as well).
My System SpecsSystem Spec
05 Feb 2011   #6

Windows 7 Ultimate x64
 
 

Using what you stated above. I ran the tests for about an hour while gaming. Here are the results. My DPC Rate looks out of whack to me. I really don't have a clue why its like that or if it's bad. The others look pretty consistent. What do you think?


Attached Thumbnails
Monitor CPU &amp; Ram over time-my-results.gif  
My System SpecsSystem Spec
05 Feb 2011   #7

Windows Server 2008 R2
 
 

That's pretty high - without a baseline, it's hard to say with 100% certainty if it's "bad", but that is indeed pretty high. High DPC rates are driver-driven, so if that seems to happen whenever you game, you might want to get some perfmon to see what it's like when you're not to compare.
My System SpecsSystem Spec
Reply

 Monitor CPU & Ram over time




Thread Tools



Similar help and support threads for2: Monitor CPU & Ram over time
Thread Forum
Monitor Computer Usage Time Software
Solved How do i change monitor inactive time General Discussion
Time for a new monitor? Hardware & Devices
PC & XBox 360 with 1 LCD Monitor at same time? Hardware & Devices
Monitor flashed Black from time to time General Discussion
New monitor time... Chillout Room
BSOD every time I turn my monitor off. Hardware & Devices

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 01:42 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33