webMethods blog for performance tuning from webMethods control parameters
Use the below control parameters to decide your webMethods performance fine tuning
Specifies the number of sessions for the default client. The default client is the Broker
client that the Integration Server uses to publish documents to the Broker and to retrieve
documents delivered to the default client. When you set this parameter to a value greater
than 1, the Integration Server creates a new multiâsession, shared state Broker client
named clientPrefix_DefaultClient_MultiPub, to use for publishing documents to the
Broker. Using a publishing client with multiple sessions can lead to increased
performance because it allows multiple threads to publish documents concurrently. The
default is 1 session.
Specifies the number of sessions for the request/reply client. The request/reply client is
the Broker client that the Integration Server uses to send request documents to the Broker
and to retrieve reply documents from the Broker. Increasing the number of sessions for
the request/reply client can lead to improved performance because it allows multiple
requests and replies to be sent and retrieved concurrently. The default is 1 session.
which corresponds to Poll delay Interval). By setting this to a specific value say X ms, you can force the trigger to keep polling the Broker after every X ms indefinitely until a document is available.
which corresponds to poll delay Interval Increment.