When the file system that hosts the replay log is fast, generating a replay log should not have any noticeable effect on correlator performance. Consequently, the recommendation is to always run correlators that send information to replay logs. Just make sure you have enough disk space for the replay log. You need to monitor repeated use to determine how much space is required.

With the correlator generating a replay log, you can implement your application so that it sends a minimum amount of information to the correlator status log. You do not need to log application information because you can always recover application information from the replay log. Implementing an application that sends large amounts of application information to the correlator status log can negatively impact performance.

Another way to improve performance is to generate an input-only replay log rather than a full replay log. See Comparison of full replay logs and input-only replay logs.