Open topic with navigation

TIBCO iProcess® Engine 11.10.0

# WIS_FILTER_THREAD_BOUNDARIES

WIS and WQS Process Configuration

## Summary

This attribute defines the count boundary at which a work queue will be split into multiple blocks of work for filtering purposes, based on the number of work items in the queue.

## Applies To

This attribute can be set for the `WIS` process (only).

## Permissible Values

This attribute must be a string in the following format:

`“``Threshold1``[:``Threshold2``[:``Threshold3``[:``Threshold4``]]]”`

where the four `Threshold` parameters are numeric values indicating the number of work items in a work queue at which an additional block of filtering work will be created. Each subsequent value, if used, must be greater than the preceding value.

## Default Value

The attribute is assigned the following default value when the iProcess Engine node is installed.

Machine ID | Process | Instance | Value
0 | WIS | 0 | 100,000

## Notes

By default, the `WIS` process uses the thread that is processing an RPC request to perform any work queue filtering required by that RPC request. When the number of items in a work queue reaches one of the threshold values defined in this attribute, the queue is split into equal blocks of filtering work. The first block is still handled by the RPC processing thread. Subsequent blocks are handled by threads from the queue filtering thread pool (the number of which is defined by the WIS_FILTER_THREAD_POOL_SIZE attribute).

Modifying this attribute can therefore reduce the time taken by the `WIS` process to filter work queues, particularly when queues are large or use complex filter criteria involving expressions or CDQPs.

See Configuring How Work Queues are Filtered for more information.

## Examples

The following example means that the queue will be split into two blocks of work for filtering purposes when the number of work items in the queue reaches 100000. The queue is split into two equal blocks of 50000 work items. The first block is handled by the original RPC processing thread and the second is handled by one of the queue filtering threads.

`100000`

The following example means that the queue will be split into two filtering blocks (each of 50000 work items) when the number of work items in the queue reaches 100000, and into three blocks (each of 60000 work items) when the number of items reaches 180000. The first block is handled by the original RPC processing thread. The second and third blocks are handled by the queue filtering threads.

`100000:180000`

## See Also

RPC_SVR_CONTROL, WIS_FILTER_THREAD_POOL_SIZE

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO iProcess® Engine

Copyright © 1994-2025. Cloud Software Group, Inc. All Rights Reserved.