AbstractBundler Class |
14c (14.1.1.0)
F23534-02
An abstract base for processors that implement bundling strategy.
Inheritance HierarchySystemObject
Tangosol.Net.CacheAbstractBundler
Tangosol.Net.CacheAbstractEntryBundler
Tangosol.Net.CacheAbstractKeyBundler
Tangosol.Net.CacheAbstractBundler
Tangosol.Net.CacheAbstractEntryBundler
Tangosol.Net.CacheAbstractKeyBundler
Namespace: Tangosol.Net.Cache
Assembly: Coherence (in Coherence.dll) Version: 14.1.1.14 (14.1.1.14)
SyntaxC#
public abstract class AbstractBundler
The AbstractBundler type exposes the following members.
Constructors| Name | Description | |
|---|---|---|
 | AbstractBundler |
Construct the bundler. By default, the timeout delay value is set to
one millisecond and the auto-adjustment feature is turned on.
|
Properties| Name | Description | |
|---|---|---|
 | AllowAutoAdjust |
Specifies whether or not auto-adjustment is on. Default value is "true".
|
| DelayMillis |
The timeout delay value.
|
| SizeThreshold |
The bundle size threshold value.
|
| SyncRoot |
Gets an object that can be used to synchronize access to the
ICollection.
|
| ThreadThreshold |
The minimum number of threads that will trigger the bundler to
switch from a pass through to a bundled mode.
|
Methods| Name | Description | |
|---|---|---|
| Adjust |
Adjust this Bundler's parameters according to the available
statistical information.
|
| Equals | Determines whether the specified object is equal to the current object. (Inherited from Object.) |
 | Finalize | Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection. (Inherited from Object.) |
| GetHashCode | Serves as the default hash function. (Inherited from Object.) |
| getOpenBundle |
Retrieve any Bundle that is currently in the open state. This method does
not assume any external synchronization and as a result, a caller must
double check the returned bundle open state (after synchronizing on it).
|
| GetType | Gets the Type of the current instance. (Inherited from Object.) |
| InstantiateBundle |
Instantiate a new Bundle object.
|
| MemberwiseClone | Creates a shallow copy of the current Object. (Inherited from Object.) |
| ResetStatistics |
Reset this Bundler statistics.
|
| ToString |
Provide a human readable description for the Bundler object
(for debugging).
|
| UpdateStatistics |
Update the statistics for this Bundle.
|
Fields| Name | Description | |
|---|---|---|
  | ADJUSTMENT_FREQUENCY |
Frequency of the adjustment attempts. This number represents a number of
iterations of the master bundle usage after which an adjustment attempt
will be performed.
|
 | m_countThreads |
A counter for the total number of threads that have started any bundle
related execution. This counter is used by subclasses to reduce an impact
of bundled execution for lightly loaded environments.
|
| m_listBundle |
A pool of Bundle objects. Note that this list never shrinks.
|
| m_previousSizeThreshold |
The previous bundle size threshold value.
|
Remarks
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.
 Note |
|---|
| We assume that all bundle-able operations are idempotent and could be repeated if un-bundling is necessary due to a bundled operation failure. |
See Also