CPU reading
CPU reading
I am getting a bunch of readings well above 100% on CPU test. 147% 164% 112% ect.... Where does host monitor get this number from since I would believe 100% to be the max
Could you please provide some information?
- HostMonitor version?
- Windows version?
- are you checking local or remote system?
- what test method do you use? CPU Usage? Performance Counter?
- test performed by HostMonitor or by RMA?
- if test performed by RMA, what version?
- how many processors installed on the system?
Regards
Alex
- HostMonitor version?
- Windows version?
- are you checking local or remote system?
- what test method do you use? CPU Usage? Performance Counter?
- test performed by HostMonitor or by RMA?
- if test performed by RMA, what version?
- how many processors installed on the system?
Regards
Alex
H'm, NT 4 SP 6a...
Truth to say we was not able to test HostMonitor on this Service Pack. We tested software on SP 3 and SP 4 but system crashed when we installed SP 6. We installed SP 6 on another system and that system crashed after user logged in. So, we do not have any system with SP 6
You can try to use Performance Counter instead. May be it will work correctly..
Regards
Alex

Truth to say we was not able to test HostMonitor on this Service Pack. We tested software on SP 3 and SP 4 but system crashed when we installed SP 6. We installed SP 6 on another system and that system crashed after user logged in. So, we do not have any system with SP 6

You can try to use Performance Counter instead. May be it will work correctly..
Regards
Alex
cpu test
I have yet to get performance counters working on any of my NT4 Servers even after I have tried all the solutions I have found here about NT and Performance Counters. SO I have given up on that and convinced my Director that in order to perform those tests we need to upgrade to Win 2000. So he has settled for waiting until then for the performance tests. So when it comes to those we just run them on the 2k boxes. Which when we do a perf counter on Terminal Services we usually get another error 301. Yet to figure that one out but will.