Counter cache not updating
When these values are exceeded, the client experience degrades.For example, users may experience slow system performance and message delivery delays.These include desktop search engines, customer relationship management (CRM), or other third-party applications. Indicates the rate at which client backoffs are occurring.Higher values may indicate that the server may be incurring a higher load resulting in an increase in overall averaged RPC latencies, causing client throttling to occur.For information about how clients are affected when overall server RPC averaged latencies increase, see Understanding Client Throttling Policies.If checkpoint depth increases continually for a sustained period, this indicates either a long-running transaction, (which will impact the version store), or a bottleneck involving the database disks.
Maximum value is RAM-2GB (RAM-3GB for servers with sync replication enabled).When these values are exceeded, the database copy may lag by not replaying logs to the passive database copy fast enough. The following table shows a replay log I/O latency requirements counter.When these values are exceeded, the database copy may lag by not replaying logs to the passive database copy fast enough. Indicates the RPC latency, in ms, averaged for all operations in the last 1,024 packets.This and Database Cache Hit % are useful counters for gauging whether a server's performance problems might be resolved by adding more physical memory.Use this counter along with store private bytes to determine if there are store memory leaks.