Poor Replication or XLA Performance
Most of this section addresses issues that may impact replication performance. Some issues, such as log buffer too small and reading from the transaction log files on the file system, can impact the performance of both replication and XLA applications.
| Possible cause | See... |
|---|---|
|
Network is slow. |
Check Network Bandwidth for information. |
|
|
Check Use of Return Receipt Blocking for information. |
|
Replication scheme is inconsistent. |
Check Replication Configuration for information. |
|
Log buffer is too small. |
Check Size of Log Buffer for information. |
|
There are frequent or inefficient file system writes. |
Check Durability Settings for information. |
|
Reading from transaction log files on the file system rather than the log buffer. |
Check Reads from Transaction Log Files for information. |
|
Rate of conflicts is high. |
Conflict Reporting Slows Down Replication for information. |
Check Durability Settings
You can improve replication performance by setting TRANSMIT NONDURABLE on the replication ELEMENT to eliminate the flush-log-to-file system operation from the replication cycle. See Setting Transmit Durability on DATASTORE Element in the Oracle TimesTen In-Memory Database Replication
Guide for details.
Enabling the DURABLE COMMIT option in your replication scheme also impacts performance. See DURABLE COMMIT in the Oracle TimesTen In-Memory Database Replication
Guide for more information.