Long term monitoring
I need to isolate some problems with a Win 7 box maxing out its CPU from time to time and basically becoming unresponsive to the user's demands. This could be over several days.
I want to be able to look at the stats and say to myself somthing like: "I see Foo.exe regularly maxes out the CPU and takes a lot of memory too"
At the same time, i want to avoid things like:
I haven't done this before and am not sure what tool to use. I've perused things like Perfmon and xperf
I want to be able to look at the stats and say to myself somthing like: "I see Foo.exe regularly maxes out the CPU and takes a lot of memory too"
At the same time, i want to avoid things like:
producing a log file of the kind of size that becomes a problem
producing stats that are difficult to analyze
producing stats that are not relevant
I haven't done this before and am not sure what tool to use. I've perused things like Perfmon and xperf
ASKER
No, i think that's not really practicable. They are not technical and there's not much i can do if they notice this (which they might not) if they telephone me.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Performance Monitor lets you collect data but there is a bit of setup to get you going.
ASKER
how much time are you going to put into troubleshooting this compared to a ...Good point. Am hoping to find one rogue process ;)
For finding a rogue process , I often use Process Explorer (good tool).
Look down under Explorer (left side tree) as a starting point.
Now look for strange alpha numeric processes. Kill these, do not restart, run Malwarebytes to keep up the problems. When it is done, restart and test.
Look down under Explorer (left side tree) as a starting point.
Now look for strange alpha numeric processes. Kill these, do not restart, run Malwarebytes to keep up the problems. When it is done, restart and test.
ASKER
For finding a rogue process , I often use Process Explorer (good tool).
You're missing the point John - i shall not be at the box. Also, i don't mean 'rogue' as in malware, but as in badly behaved
I find most badly behaved software (e.g. mixing Symantec Endpoint with Windows Defender when upgrading to Windows 10) shows up right away.
I do not know (beyond what we discussed here) what will show you CPU spikes on a long term basis.
I do not know (beyond what we discussed here) what will show you CPU spikes on a long term basis.
ASKER
This question is not abandoned. I'm still waiting from someone experienced in absent, lengthy process monitoring. If that someone doesn't arrive, i shall close it as unanswered
Perfmon is a perfectly valid answer given that it logs data and allows it to analyzed. Difficult to analyze means suggests you don't want to spend the proper time learning how to use it.
ASKER
Well, of course, it was i that mentioned Perfmon. I would like to hear from people who have carried out what i want to do
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi cehj,
What you really need is a profiling tool to show you where the hotspots are in the code. There are two natural choices; Windows Performance Toolkit (WPT) and PerfView. Both are Microsoft tools and free for download.
There is a minor drawback with WPT; during recording you need to disable Executive Paging, and it can be tricky getting Change Control permission to do that. There is no noticeable impact. I've been running my laptop with Executive Paging disabled for about 6 months and I haven't noticed any difference.
From a practical point of view, WPT would probably be favorite for you as the recorder (WPR) can be run in command line mode and so you could simply set it up as a Scheduled Task on a users PC. However, I have to say I really like PerfView for analysis. Luckily you can capture with WPR and analyse with PerfView if you want.
Both tools can run in a ring buffer mode. Obviously, you'll need to test it and you'll need to put in place a procedure that needs to be followed when the problem occurs.
There are a good sequence of videos covering WPT on Microsoft's Channel 9 - see https://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-39-Windows-Performance-Toolkit
For PerfView, again it's Channel 9 - see https://channel9.msdn.com/Series/PerfView-Tutorial
They even cover analysis of hot code!
Best regards...Paul
What you really need is a profiling tool to show you where the hotspots are in the code. There are two natural choices; Windows Performance Toolkit (WPT) and PerfView. Both are Microsoft tools and free for download.
There is a minor drawback with WPT; during recording you need to disable Executive Paging, and it can be tricky getting Change Control permission to do that. There is no noticeable impact. I've been running my laptop with Executive Paging disabled for about 6 months and I haven't noticed any difference.
From a practical point of view, WPT would probably be favorite for you as the recorder (WPR) can be run in command line mode and so you could simply set it up as a Scheduled Task on a users PC. However, I have to say I really like PerfView for analysis. Luckily you can capture with WPR and analyse with PerfView if you want.
Both tools can run in a ring buffer mode. Obviously, you'll need to test it and you'll need to put in place a procedure that needs to be followed when the problem occurs.
There are a good sequence of videos covering WPT on Microsoft's Channel 9 - see https://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-39-Windows-Performance-Toolkit
For PerfView, again it's Channel 9 - see https://channel9.msdn.com/Series/PerfView-Tutorial
They even cover analysis of hot code!
Best regards...Paul
You could set it up and ask users to alert you when CPU is high.