Not run all tests at startup

Niels Kinkel · Post by **Niels Kinkel** » Tue Sep 02, 2008 3:51 am

We have about 2000 tests currently in the system, which will grow to probably twice that size within a few months. When we need to update something on the server the AHM is running on it takes about half a day before the system starts responding normally again. The cause is that all tests are executed at startup at the same time. Which causes it to be slow and when the new cycle of tests begins it is slow to execute and slow to recieve causing the system to remain painfully slow for hours.

KS-Soft · Post by **KS-Soft** » Tue Sep 02, 2008 9:20 am

We have about 2000 tests currently in the system, which will grow to probably twice that size within a few months. When we need to update something on the server the AHM is running on it takes about half a day before the system starts responding normally again

Usually we are testing HostMonitor using 5000 test items and GUI responds within seconds.
Could you please provide more information about the problem?
- HostMonitor version?
- Windows?
- Service pack?
- CPU?
- How much memory do you have installed on the system?
- What kind of tests executed most often?
- What information is displayed by Estimated Load dialog (menu View -> Estimated Load)?
May be you setup too short test interval for your tests and too high value of "Don't start more than [N] tests per second" option? E.g. if you setup 2000 tests to be checked every 20 sec, then HostMonitor should perform 100 tests every second.

The cause is that all tests are executed at startup at the same time

Do you mean you start second instance of HostMonitor every time you need to modify some settings? Why? Is it because HostMonitor is started as service on remote system? Why don't you use Remote Control Console (RCC)?

BTW: There is command line parameter that allows you to start HostMonitor without executing tests
http://www.ks-soft.net/hostmon.eng/mfra ... #CmdParams

Regards
Alex

Niels Kinkel · Post by **Niels Kinkel** » Tue Sep 02, 2008 9:32 am

HM Version: 7.50
Windows: Server 2003 SP2
CPU: 2.8 GHz
Ram: 512 Mb
Load: 2 tests/s
Most executed: Services 36 /m, UNC 19 /m, Drive space 15 /m, CPU 13 /m
Max tests started per second: 32

When we update HM or when we shut it down at the end of the day instead of just locking the screen it takes a very long time before it get itself running properly again.

KS-Soft · Post by **KS-Soft** » Tue Sep 02, 2008 11:35 am

Ram: 512 Mb

Not much...

Load: 2 tests/s
Most executed: Services 36 /m, UNC 19 /m, Drive space 15 /m, CPU 13 /m
Max tests started per second: 32

Should not be a problem

Could you send HML file with tests to support@ks-soft.net? May be we will be able to reproduce the problem.

When we update HM or when we shut it down at the end of the day

shut it down at the end of the day? If you don't need to monitor some/all servers at night you may use schedule
http://www.ks-soft.net/hostmon.eng/mfra ... ofiles.htm

Regards
Alex