|
The mentioned setting will only reduce the "wait" (in
milliseconds) between 2 checks (within the same cycle).
The default is 250ms, the lowest you can go is
10ms.
Restarting SA after making the change is
needed.
And it should give a difference.
A simple calculation shows that on a 100 entries list it
should give a
(100 * 250) - (100 * 10) = 25000 - 1000 =
24000
24000ms or 24s difference in cycle
time.
Dirk. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Clough, Bruce Sent: Tuesday, December 06, 2005 10:06 PM To: [email protected] Subject: RE: [SA-list] Server's Alive slowness The system is running
Windows 2003 server with dual 2.4 GHz Xeon processors and 1 GB of
RAM. --Bruce From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Stone Which version are you
running(5.x.xxxx), how many checks, and what are the server specs(CPU and
RAM). That setting has been the most dramatic decrease in cycle times for
my installations. -Kevin From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of I recently migrated Server’s Alive
to a newer faster server with more memory and upgraded from version 4 to version
5. However, it is taking significantly more time to complete the check cycle
that it did on the old system. I changed the registry value
HKEY_LOCAL_MACHINE\SOFTWARE\DBU Consulting\Servers Alive\StartUp\PerItemCycle
from 250 to 10 and rebooted the server, but there has been no effect on the
length of the check cycle. Is there something else that needs
to be set to increase performance? Bruce
Clough Bechtel |
- RE: [SA-list] Server's Alive slowness Clough, Bruce
- RE: [SA-list] Server's Alive slowness Dirk Bulinckx
- RE: [SA-list] Server's Alive slowness Kevin Stone
- RE: [SA-list] Server's Alive slowness Dirk Bulinckx
- RE: [SA-list] Server's Alive slowness Kevin Stone
- Re: [SA-list] Server's Alive slowness Brett Hanson
- RE: [SA-list] Server's Alive slowness Dirk Bulinckx
- RE: [SA-list] Server's Alive slowness Brett Hanson
