Latency is always reported at 1ms (Legacy KB ID CNC TS22645)

Products

• CA eHealth

Issue/Introduction

To revert to using the low resolution clock, set NH_USE_LOW_RES_CLOCK to YES in the Windows System Variables UI. 

For instructions, please refer to How to Set or Change eHealth Environment Variables-NT

The issue documented above has been resolved in the following release(s):

    eHealth 5.7 Service Pack 6
    eHealth 6.0

eHealth Service Packs are available for download at: Service Pack and Product Downloads. Please review the README file for each Service Pack prior to installing. CA recommends that users always keep eHealth current by installing the latest Service Pack available.

Related Issues/Questions:
Latency is always reported at 1ms
Error: "Decrementing high performance clock samples detected, contact your system vendor for bios upgrade"
What does the environment variable NH_USE_LOW_RES_CLOCK do

Problem Environment:
eHealth 5.6.5 and later
eHealth 5.7
eHealth 6.0
Microsoft Windows
Problem Ticket: PRD00014099

Causes of this problem:


Changes affecting this problem:
Added ability to use the high resolution Windows system clock for eHealth Ping latency measurements - this is now the default.

Added new environment variable NH_USE_LOW_RES_CLOCK to automatically revert to low resolution clock if problem with skew of high resolution clock on multi-CPU system is detected (the cause of constant 1ms latency values).

Additional Information:



(Legacy KB ID CNC TS22645 )

Environment

Release:
Component: EHCON