Optimize HPOM node name resolution
Several enhancements have been implemented to improve the
performance of HPOM for Windows node name resolution. The speed of
the node name resolution has a significant impact on the following
areas:
- Message filter (directly impacts flow of new incoming
messages)
- Health check
- Actions
These enhancements will help resolve (or at least reduce) the
following performance related problems:
- Slow initialization of the HPOM node cache during the startup
phase of the OvEpMessageActionServer service (30-60 minutes).
During the initialization, the message flow is disabled.
- Slow name resolution if using virtual nodes.
- Significant delays for new incoming messages due to slow node
name resolution.
- Slow health check, slow processing of ICMP replies sent from
managed nodes.
Managed environments that do not make use of DHCP will experience
the largest benefits. Here, an optional memory based cache can be
configured which drastically reduces the number of the Windows API
calls
gethostbyname()
and
gethostbyaddr()
. However, environments using DHCP can
also take advantage of a modified ip-address verification which
tries to avoid unnecessary reverse node name resolution.
To make use of the enhancements, you must configure several
values using the Server Configuration dialog box. If the values are
not set, then the enhancements will not take effect. See the
Related Topics for enhancement details.
Related Topics: