In message , Mark Blain
writes:
[]
Have you tried the built-in Resource Monitor (resmon.exe)? It
doesn't meet your requirement to trigger at a particular level, but
I've found it useful for identifying high CPU and high disk usage
processes. Performance Monitor (perfmon.exe) can also be useful, if
you add the "Process" counter and set the view to "Report", but it's
not as simple to set up and use.

https://blogs.technet.microsoft.com/...2/02/01/using-
resource-monitor-to-troubleshoot-windows-performance-issues-part-1/

Thanks. I haven't tried lately, but when I've tried with Process
Explorer, Task Manager, Process Lasso, Resource Monitor, and so on, I've
found it always rather too complicated to answer the question "what
triggered that surge" - because it's usually abated (or abating) by the
time I get to hunting. I know some of the tools - possibly including
Resource Monitor - _do_ tell you what _was_ the cause (hover over the
peaks in the graph, in at least one of them), but it's fiddly to do.
Hence my emphasis on the word Simple.

Though I suspect that even if I _was_ able to _easily_ establish what
caused peaks, I'd still be in the dark, wondering _why_. (Unless it was
something I could safely kill altogether except when I want it - and I
suspect that's not going to be the case.)
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

That's how he [Dr. Who] seems to me. He's always been someone who gets the
/Guardian/. There are some parts of the universe where it's harder to get hold
of. - Peter Capaldi (current incumbent Doctor), RT 2016/11/26-12/2