Try OpenEdge Now
skip to main content
User Guide
Planning for OpenEdge Replication : Understanding the importance of after-imaging in OpenEdge Replication planning : Determining acceptable latency

Determining acceptable latency

Latency within OpenEdge Replication is defined as the time between an update being performed on the source database and the update occurring on the target database. OpenEdge Replication latency depends on the following factors, all of which should be taken into consideration:
*The number and frequency of updates to the source database — If the database is frequently updated and the after-image blocks are frequently filled, the latency is much shorter. If there is little uncommitted activity on the source database, the latency may be longer.
*Network volume availability and bandwidth — If the network is slow or near capacity, the latency between the source and target database increases.
*Target database/machine downtime — The longer the target database or machine is unavailable, the higher the latency will be. If the downtime is expected to be a multi-day event, you should consider disabling OpenEdge Replication on the source database.
During downtime of the target database or machine, the source/production database is unprotected. If the target is used for read-only access, a down target would mean no read-only access.
For more information about latency, see Reference.