Worker pool expansion

In AX-3.8, a “BacnetWorkerPool” (Worker Pool) component is available, found on the bacnet palette. In cases where Bacnet “queue full” messages have occurred, or to possibly increase messaging performance, it may help if you copy and paste a Worker Pool under one or more Worker slots.

Figure 13. Worker Pool copied from palette and pasted under Bacnet Comm, Server, Confirmed Worker

If a worker directly under the BacnetNetwork, first you must access the slot sheet of the network and edit config flags for its “worker” and/or “writeWorker” slots to “unhide” these slots. This lets you see/access the Worker components on the network’s property sheet, where you can paste a Worker Pool component on (under) them.
At the time of this document, the (AX-3.8) BacnetWorker “COV Worker” does not support a “Worker Pool” child. An error results if you attempt to add one under it.
Between the two Bacnet Comm, Server workers, typically the “Confirmed Worker” benefits most from adding a Worker Pool under it. This is the example shown in Figure 13.

Worker Pool properties

WorkerPool has a single configuration property:

Max Threads — Specifies the maximum number of threads in the worker pool; the default is 2. Often this is sufficient, but may be increased if necessary. However, large numbers may prove to be detrimental, especially if a JACE platform with limited resources.