Server, Worker and Confirmed Worker (bacnet-BacnetWorker)
Sometimes, default configuration of Workers provides good BACnet driver performance. However, in some scenarios configuration adjustments may be needed.
These properties configure the queuing and processing of server messages (responses to requests from BACnet clients). Workers manage the queue and thread processing for reads and writes to BACnet. Sometimes the default configuration of worker components provides good BACnet driver performance. However, if a station operates as a BACnet server with a large number of BACnet clients, configuration changes to one or both workers may be beneficial.
Figure 31. Worker properties
To access these properties, expand and double-click Worker.
To access a hidden worker slot, you must first clear the hidden flag from the network’s slot sheet. Separate workers help to prevent certain confirmed event notifications from blocking the processing of all incoming requests to the BACnet server layer.
| Property | Value | Description |
|---|---|---|
| Max Queue Size | number (defaults to 1000) |
Specifies the maximum number of items that can be queued for worker processing. In a few cases, particularly in a large system, increasing this size may be beneficial. Queue size does not allocate a fixed memory size. Rather, the amount of memory used is dynamic, changing as message items are added and removed from the queue. |
| Worker Thread Name | read-only in the format: server:worker or server:confirmedworker | Reports the identifiers for threads managed by the worker.
Processes unconfirmed server messaging, including event (alarm) notifications, confirmed COV, and so on. For example Who-Is and Who-Has responses as well as unconfirmed COV server messaging. |