Managing Latency Technical Brief
Share This!
- Copy link to clipboard
- Email link
- Print
Managing Latency is One of the Most Critical Aspects of Data Replication Performance
The two most important types of latency are replication latency and application latency.
Replication Latency
- Replication latency is the elapsed time between when a data change (e.g., insert, update, delete) is committed to the source system database, and when it is applied to the target database.
- It is the time period when the change data is in the replication pipeline.
- It is affected by system utilization, process priorities, and network bandwidth.
This Time Period is Very Important to Businesses
It represents production change data that is not yet backed-up, and may be lost in the event of an outage of the source or target system. The longer this time interval is, the more data may be lost.
Application Latency*
- Application latency is the time spent after the source application calls transaction commit, while Shadowbase Zero Data Loss (ZDL) ensures the data changes are safe-stored on the target system, before allowing the source transaction to commit.
- A consequence of this process is that the time taken for the source application’s transaction commit to complete may be extended.
- This additional commit time is known as the application latency.
- Shadowbase ZDL thus ensures no data will be lost in the event of an unplanned outage, but may increase application latency as a consequence
Controlling both replication and application latency is very important. This Technical Brief provides details and information regarding how to monitor, manage and minimize both replication and application latency in Shadowbase systems.
*Application latency only applies when using the Shadowbase ZDL solution or in synchronous replication architectures.
Solution Brief:
Managing Latency Technical Brief