[DUG] Running Processes

[John Bird]

Apart than automated tools the best manual tool would be to have the client
PC running Sysinternals Process Explorer, and turn on the CPU history
columns for the whole PC (It can be 10 minutes long or more if you make it
the full width of the screen), and CPU history for each process.  This means
after a "go slow" you can look back to see what was hogging the PC for some
time afterwards - as you arrow over the graph it shows the exact time,  and
name of the process with the most CPU  at that moment.
 
If needed you can add some of the other Sysinternals tools like Filemon to
see which files are being accessed...
 
Incidentally I have NOD32 running on my PC.  Its an older version - its not
up to date and I am running another AV also, I left NOD32 on as it seems to
be having no significant system impacts at all, so no problem here.
 

John

-----Original Message-----
From: delphi-bounces at ns3.123.co.nz [mailto:delphi-bounces at ns3.123.co.nz] On
Behalf Of Jeremy Coulter
Sent: Tuesday, 27 February 2007 9:57 a.m.
To: 'NZ Borland Developers Group - Delphi List'
Subject: RE: [DUG] Running Processes


I am using another expetion handler, but the program has not "crashed" so
much as there is somethign hogging all the processes, hence why I want to
see whats running.
I have infact found some code that will get eh me cpu usage based on the PID
which I have from the code I am currently running, but its VERY slowwww
 
In saying that, has anyone deployed apps that run all the time, onto
machines that have NOD32? This is basically the only thing different between
this one site and all the other sites, and I downloaded the demo of NOD32
and installed it on a machine that has our software on it, and NOD32 runs
are 96% usage and all up about 40mb of mem usage.
I noticed that our app. needed more CPU usage when NOD32 was running, but I
guess that because it trying to get some CPU cycles
 
Jeremy

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ns3.123.co.nz/pipermail/delphi/attachments/20070227/ce18c493/attachment.html