You can adjust the interval by which member servers query the farm's
data store for missed changes. The default interval is 30 minutes. In most
cases, this default setting is sufficient.
Caution: Editing the Registry incorrectly can cause serious problems that may require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.
You can configure the interval by creating the following registry key
on each server you want to adjust, with the value expressed in hexadecimal
Value: 0x1B7740 (default 1,800,000 milliseconds)
You must restart the IMA Service for this setting to take effect.
Most changes made through the Delivery Services Console are written to
the data store. When you open one of these tools, it connects to a specified
server. The Citrix Independent Management Architecture (IMA) Service running on
this server performs all reads and write operations to the data store for the
If the data store is experiencing high CPU usage when few read or
write operations to the data store are occurring, it is possible that the data
store is not powerful enough to manage a query interval of 30 minutes. To
determine whether or not the data store query interval is causing the high CPU
usage on the data store, you can set the query interval to a very large number
and test CPU usage. If the CPU usage returns to normal after you set a large
query interval, the data store query interval is probably the cause of the high
CPU usage. You can adjust the query interval based on performance testing.
To test the query interval, set the interval to 60 minutes and then
restart all the servers in the farm. If the data store is still experiencing
constant high CPU usage, increase the query interval further. If the CPU usage
returns to normal, you can try a smaller value. Continue these adjustments
until data store CPU usage is normal.
Important: Do not set the data store query interval higher
than necessary. This interval serves as an important safeguard against lost
updates. Setting the interval higher than necessary can cause delays in
updating the local host cache of the farm’s member servers.