Poor performance and stable queue size increasing

Sometimes poor Replication Server performance is caused by the Stable Queue Transaction (SQT) cache size being too small. If the SQT cache is not big enough to hold all open transactions, transactions that cannot fit completely into the cache are processed one command at a time.

The inbound stable queues grow (more than 1MB) because Replication Server cannot process the transactions fast enough.

To solve this problem:

Make sure that the problem is not caused by orphaned transactions. For more information about orphaned transactions, see “Log truncation problems”.
Find the optimal size for the sqt_max_cache_size parameter for your application. See the Replication Server Administration Guide Volume 2 for more information on sizing the SQT cache.
If you need to adjust the sqt_max_cache_size parameter:
1. Suspend the connection to the data server.
2. Log in to Replication Server and run this command:
```
> configure replication server
   set sqt_max_cache_size to ‘new_value’
> go
```
3. To activate the new values, resume the connection. If you want to dump the SQT cache, use the sysadmin sqt_dump_queue command.