Tuning Message Agent performance

Who needs to read this section?

If performance is not a problem at your site, you do not need to read this section.

There are several options you can use to tune the performance of the Message Agent. This section describes those options.

Sending messages and receiving messages are two separate processes. The major performance issues for these two processes are different.

  • Replication throughput   The major bottleneck for total throughput of SQL Remote sites is generally receiving messages from many remote databases and applying them to the database at the consolidated site. You can control this step by tuning the receive process of the Message Agent at the consolidated site.

  • Replication turnaround   The time lag from when data is entered at one site to when it appears at other sites is the turnaround time for replication. You can control this time lag.


Tuning throughput by controlling Message Agent threading
Tuning throughput by caching messages
Tuning incoming message polling
Tuning the message sending process