(1) The work queue depth is the number of replications waiting to be processed by the cluster replicator.

(2) The Activities act like a work queue, where work is assigned and completed.

(3) The work queue mechanism is inherited from the WLM queuing manager service.

(4) The work queue is generally implemented as some sort of linked list with an associated monitor object.

(5) First, simply enqueue the work on a work queue using queue_work (which ties the work to the current CPU).

(6) The optimum size of a thread pool depends on the number of processors available and the nature of the tasks on the work queue.

(7) A key problem with this model is that increasing the number of worker threads increases the contention on the work queue (this is shown in Figure 3).

(8) Basically, at any given time, any servant region will only bind to a single specific service class work queue and select requests from there.

(9) If the source adapter agent is a bottleneck, events will build up in the work queue that the agent is monitoring.

(10) Source adapter agent - Source adapters are configured to monitor an incoming work queue and pass incoming events to the server.

(11) Recall from Figure 3 that the core structure for the work queue is the queue itself.

(12) In this case, we may not want to queue every incoming request to our work queue, because the tasks queued for execution may consume too many system resources and cause resource starvation.

(13) The following example illustrates a few of the core work queue API functions.

(14) When multiple replicators are used, the cluster replication queue and work queue depth times are reduced.

(15) Filtering indicates 2,1031- requires a bit more sieving(), so don't be surprised when more work units for it appear in your work queue.

(16) A new request comes in and stays in the new service class work queue.

(17) Within each application environment, there will be only one work queue mapping to one service class; the work queue will just follow the service class's name.

(18) All the servant regions are now bound to existing work queues, and no servant region can immediately convert to the new service class work queue.

(19) Listing 1 shows an example of a simple pooled work queue.

(20) Suppose we wanted to add Business Process management (BPM) to the solution, such that when the message came in, it is stored in some sort of work queue for an editor to approve.