Tuning Message Agent performance
Whoneeds to read this section?
If performance is not a problem at your site, you do not need to read this
section.
Thereare several options you can use to tune the performance of the
MessageAgent. Thissection describes those options.
Sendingmessages and receiving messages are two separate processes. The
majorperformance issues for these two processes are different.
Replicationthroughput Themajor bottleneck for total throughput of
SQLRemote sites is generally receiving messages from many remote
databasesand applying them to the database at the consolidated site. You
cancontrol this step by tuning the receive process of the Message Agent
atthe consolidated site.
Replicationturnaround Thetime lag from when data is entered at one
siteto when it appears at other sites is the turnaround time for replication.
Youcan control this time lag.

Tuningthroughput by controlling Message Agent threading

Itis assumed in this section that you are tuning the performance of a
MessageAgent that is running in continuous mode at a consolidated site.
Workerthreads can be used by the Message Agent to apply incoming
messagesfrom remote users. Thiscan improve throughput by allowing
messagesto be applied in parallel rather than serially.
Settingthe number of
workerthreads Thenumber of worker threads is set on the Message Agent command line,
usingthe -w option. Thefollowing command line starts the Message Agent
forAdaptive Server Enterprise with twenty worker threads applying
messages:
ssremote -c "eng=..." -w 20
Thedefault is to use no worker threads, so that all messages are applied
serially.The maximum number of worker threads is 50.
Performancebenefits
fromwor kerthreads Forthe Message Agent for Adaptive Server Anywhere, the performance
advantagewill be most significant when the server is on a system with a
stripeddrive array.
ForAdaptive Server Enterprise, the Message Agent will benefit even more if
theServer is used with multiple engines configured.
228