RE: What can cause an LEI Replication Job to run a long time? Daniel W Heichel 9.Jan.14 03:34 AM a Web browser LEI All ReleasesWindows
Here are a couple of other things that can impact performance.
- Excessive logging not only fills up a lot of physical space, it takes a small amount of time for each write. Normally this is not a big deal, but if you had (for example) a Replication activity with Conflict Logging turned on, it might have to write hundreds or - if not restricted - thousands of Replication Conflict reports.
- If you have a Sort Order issue, it can cause the Replication activity to perform unnecessary inserts and deletions. (Because the source and target are out of order, LEI will find conflicts, proceed to insert or delete, then later find the record in question and have to go back and undo the change). This will naturally affect performance. Look for inserts and deletions when there shouldn't be any, or more inserts and deletions than make sense. An Order Metaconnector can resolve this.