Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
CPU Status
Message
From
08/09/2006 12:00:12
 
 
To
08/09/2006 11:49:55
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Title:
Environment versions
Visual FoxPro:
VFP 8 SP1
OS:
Windows XP SP2
Network:
Windows 2003 Server
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01152193
Message ID:
01152355
Views:
24
Hi Dragan,
But using Dunkeld's code I can control performance remotely from another process! If I know processID - I can run another EXE file which by timer will ask CPU Util. of this process.. and I can set the limit. and if the process take long time CPU more then limit, then I will command to process run coverage profiler and log.. (maybe put file to process directory and IF FILE("....") SET COVERAGE TO ...
Its my idea now

Denis
P.S. the reason - my app works strange.. it might work perfect during day.. and then... completely lock system... and maybe problem source is TAPI.. maybe Winsock.. maybe too many not closed timers which controls line..


>>>Denis,
>>>
>>>>Cool! .. is there exist a WMI Query to ask about process CPU utilization? For example, to get an information about my application process only.
>>>
>>>If your app is a VFP app there are basically only 2 CPU utilization factors.. less than 1% (when it's sitting at a wait state) and 100% (when it's running code). *bg*
>>
>>:)))
>>David,
>>I describe my problem. I wrote Tapi + winsock solution. My application perfect work.. but SOMETIMERS.. it begin using 90% of CPU... And I can't catch the moment when it happen and what fail in application.
>>At this reason, I want to place timer which will check CPU ... and if app during long period take CPU time I want to run coverage profiler and shutdown app.. then look in log - which process make this sh...t..
>
>So David's actually right - you need a WMI function which would return a logical. If it returns a .f., no worry, it's below 1%. If it returns .t., it's close to 100%. Rest of the time it must be some other process, not Fox :).
Previous
Reply
Map
View

Click here to load this message in the networking platform