 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Unix there's a useful little utility usually referred to as
"time(1)". Using it, you can run a command and time how long it takes to
run and how much memory it uses.
Does anybody know of something similar on Windows?
One of the various Windows Resource Kits contains TIMEIT.EXE which
allows you to time the execution of a process, but it doesn't give you
any memory usage information.
System Internals do all sorts of interactive process monitoring tools,
but I can't find anything scriptable.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Invisible wrote:
> System Internals do all sorts of interactive process monitoring tools,
> but I can't find anything scriptable.
Process monitor or powershell are probably your best bet.
--
Darren New, San Diego CA, USA (PST)
Serving Suggestion:
"Don't serve this any more. It's awful."
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> System Internals do all sorts of interactive process monitoring tools,
>> but I can't find anything scriptable.
>
> Process monitor or powershell are probably your best bet.
Process monitor also isn't scriptable (and seems to focus on recording
process events, rather than the sort of running totals I'm interested in).
PowerShell's Get-Process command happily lists out voluminous data about
all the processes in the system. Now if I can just figure out how the
**** to use the command syntax...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Invisible wrote:
> process events, rather than the sort of running totals I'm interested in).
Performance monitor is what I meant.
> PowerShell's Get-Process command happily lists out voluminous data about
> all the processes in the system. Now if I can just figure out how the
> **** to use the command syntax...
I have found that adding "tutorial" on the end of what you're interested in
and googling tends to give useful results. (I'm not being snarky here. Just
pointing out that "tutorial" seems to be the word people have settled on.)
Search MSDN, too.
And of course it depends what OS you're running, as this is the sort of
thing that seems to change a lot between releases. If you're doing XP,
http://stackoverflow.com/questions/97590/whats-the-best-tool-to-track-a-processs-memory-usage-over-a-long-period-of-time
You just monitor the process, then after the fact look at the logs.
--
Darren New, San Diego CA, USA (PST)
Serving Suggestion:
"Don't serve this any more. It's awful."
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
