Used in: operation-bundling.


The bundle-config element specifies the bundling strategy configuration for one or more bundle-able operations.


The following table describes the elements you can define within the operation-bundling element.

Element Required/Optional Description
<operation-name> Required Specifies the operation name for which calls performed concurrently on multiple threads will be "bundled" into a functionally analogous "bulk" operation that takes a collection of arguments instead of a single one.

Valid values depend on the bundle configuration context. For the cachestore-scheme the valid operations are "load", "store" and "erase". For the distributed-scheme and remote-cache-scheme the valid operations are "get", "put" and "remove". In all cases there is a pseudo operation named "all", referring to all valid operations.

Default value is "all".
<preferred-size> Optional Specifies the bundle size threshold. When a bundle size reaches this value, the corresponding "bulk" operation will be invoked
immediately. This value is measured in context-specific units.

Valid values are zero (disabled bundling) or positive values.

Default value is zero.
<delay-millis> Optional Specifies the maximum amount of time in milliseconds that individual execution requests are allowed to be deferred for a purpose of "bundling" them together and passing into a corresponding bulk operation. If the preferred-size threshold is reached before the specified delay, the bundle is processed immediately.

Valid values are positive numbers.

Default value is 1.
<thread-threshold> Optional Specifies the minimum number of threads that must be concurrently executing individual (non-bundled) requests for the bundler to switch from a pass-through to a bundling mode.

Valid values are positive numbers.

Default value is 4.
<auto-adjust> Optional Specifies whether or not the auto adjustment of the preferred-size value (based on the run-time statistics) is allowed.

Valid values are "true" or "false".

Default value is "false".