Event Processing Subsystem

ThingWorx Model Definition in Composer > System > Subsystems > Event Processing Subsystem

The event processing subsystem manages event processing for subscriptions throughout ThingWorx.

Configuration

Event Queue Processing Settings

Base Type

Default

Notes

Min Threads Allocated to Event Processing Pool

NUMBER

Max Threads Allocated to Event Processing Pool

NUMBER

500

Max Queue Entries Before Adding New Working Thread

NUMBER

200000

Maximum number of entries to queue before adding a thread to the pool

Max Cached Data For Durable Events

NUMBER

5000

Defines the batch size for data retrieval of events from Kafka. The configured value represents the maximum potential data loss if ThingWorx experiences downtime before processing the pulled data.

A value that is too low creates an artificial bottleneck and impacts the throughput.

The minimum value is 500. If you set it below 500, it will automatically revert to the default value of 5000.

Event trigger and Subscriptions execute asynchronously. For example, a property update API request receives an immediate response when the property update action completes. It does not wait for the subsequent subscriptions that respond to the Data Change Event to complete.

Ordered Subscriptions Queue Processing Settings	Base Type	Default	Notes
Max queued messages	NUMBER	100000	Maximum number of subscriptions to queue before dropping subscriptions