Integration Designer
Integration Designer now uses the new ADVANCING controller with separate picking and processing operations for improved performance and resource management.
Variables to remove & replace
| Remove This Variable | Replace With |
|---|
ADVANCING_THREADS | ADVANCING_PICKINGTHREADS (default: 1) |
ADVANCING_PICKINGBATCHSIZE | ADVANCING_PROCESSINGBUFFERSIZE (default: 20) |
New variables to add
| Variable | Default Value | Description |
|---|
ADVANCING_PROCESSINGTHREADS | 20 | Number of threads for parallel processing of advancing events |
ADVANCING_BLOCKPICKINGIFNOWORKERAVAILABLE | true | Block picking operations when no worker threads are available |
ADVANCING_DATASOURCE_MAXIMUMPOOLSIZE | 20 | Maximum database connection pool size for advancing operations |
Variables to update
| Variable | Current Value | New Value | Reason |
|---|
ADVANCING_PICKINGPAUSEMILLIS | 100 | 50 | Optimized pause duration for better performance |
How the new advancing controller works:
-
Picking threads (
ADVANCING_PICKINGTHREADS): Controls how many worker threads read events from the database. This handles only the picking/reading operations.
-
Processing buffer (
ADVANCING_PROCESSINGBUFFERSIZE): Acts as a queue between picking and processing. When the buffer is full, no new events are read. When there’s available space, that amount of events will be read.
-
Processing threads (
ADVANCING_PROCESSINGTHREADS): Controls how many threads process the advancing events in parallel. Events are processed instantly if processing threads are available. If all processing threads are busy, events accumulate in the buffer until it reaches capacity.
-
Blocking behavior (
ADVANCING_BLOCKPICKINGIFNOWORKERAVAILABLE): When enabled, prevents picking operations if no worker threads are available, ensuring better resource management.
