- This module is experimental and NOT SUPPORTED. When complete, it
- will enable Metaproxy to share resources such as result-sets
- between multiple threads, yielding performance improvements.
+ This filter implements global sharing of
+ result sets (i.e. between threads and therefore between
+ clients), yielding performance improvements especially when
+ incoming requests are from a stateless environment such as a
+ web-server, in which the client process representing a session
+ might be any one of many.
+ It performs the following actions:
+ <itemizedlist>
+ <listitem>
+ <para>
+ Reduce the number of backend server sessions.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Reduce the number of initializations with backend servers.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Optimize the use of result-sets.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ <para>
+ Configurable values:
+ <variablelist>
+ <varlistentry><term>Session TTL</term>
+ <listitem>
+ <para>
+ When a backend session is idle for more than this amount of
+ time, given in seconds, it will be closed. Default value
+ is 90 seconds.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term>Result-Set TTL</term>
+ <listitem>
+ <para>
+ When a backend session result-set is not in use for more than this
+ amount of time, given in seconds, it will be deleted/reused.
+ Default value is 10 seconds.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term>Result-Set max</term>
+ <listitem>
+ <para>
+ This specifies the maximum number of result-sets in use by
+ a backend. The number only applies to targets/servers with named
+ result sets. Targets that do not support named result sets
+ may only have one active result set. Default value is 10.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>