public abstract class AbstractBundler

Assume that we receive a continuous and concurrent stream of individual operations on multiple threads in parallel. Let's also assume those individual operations have relatively high latency (network or database-related) and there are functionally analogous [bulk] operations that take a collection of arguments instead of a single one without causing the latency to grow linearly, as a function of the collection size. Examples of operations and topologies that satisfy these assumptions are:

• Get() and GetAll() methods for the INamedCache API for the partitioned cache service topology;
• Insert() and InsertAll() methods for the INamedCache API for the partitioned cache service topology;
• Remove() method for the INamedCache API for the partitioned cache service topology;

Under these assumptions, it's quite clear that the bundler could achieve a better utilization of system resources and better throughput if slightly delays the individual execution requests with a purpose of "bundling" them together and passing into a corresponding bulk operation. Additionally, the "bundled" request should be triggered if a bundle reaches a "preferred bundle size" threshold, eliminating a need to wait till a bundle timeout is reached.

System..::..Object
  Tangosol.Net.Cache..::..AbstractBundler
    Tangosol.Net.Cache..::..AbstractEntryBundler
    Tangosol.Net.Cache..::..AbstractKeyBundler