Skip to main content
S
seanccc17-Peridot
17-Peridot
June 6, 2020
Solved

The trigger sequence of the subscription

  • June 6, 2020
  • 2 replies
  • 1739 views

Hi, 

How does thingworx manage the sequence of  executing the events ?  For example,  If  raise 100 events in a time , will the subscription be triggered with same sequence of raising event  or  the subscription will be triggered in parallel ? 

 

Regards,

Sean

Best answer by CarlesColl

It depends on the TW Version, up to what I know:

  • 7.3 and previous, they where executed in-line when where triggered
  • (in between) I don't know in which version in-between they changed the execution logic....
  • 8.4 and above, they are executed asynchronously  by the Event Processor Subsystem, which will use in parallel the amount of Threads you defined on it (by default 16). This text comes directly from R&D: "the internal event queue is an implementation of Java LinkedTransferQueue which has FIFO semantics. However, as long as there are executors available event will start getting executed in parallel (not out of order, events will be pulled in the order they were recieved) but depending on the length of the execution they could complete out of order. (i.e. the second task could finish before the first)"

Hence -> No ordered execution of events if they depend on the result of the others, if your processing subscription algorithm isn't 100% parallelizable you are out of luck.

 

Well, actually it's why I've implemented the Mutex extension 😉 

 

Best Regards

2 replies

C
CarlesColl1-VisitorAnswer
1-Visitor
June 8, 2020

It depends on the TW Version, up to what I know:

  • 7.3 and previous, they where executed in-line when where triggered
  • (in between) I don't know in which version in-between they changed the execution logic....
  • 8.4 and above, they are executed asynchronously  by the Event Processor Subsystem, which will use in parallel the amount of Threads you defined on it (by default 16). This text comes directly from R&D: "the internal event queue is an implementation of Java LinkedTransferQueue which has FIFO semantics. However, as long as there are executors available event will start getting executed in parallel (not out of order, events will be pulled in the order they were recieved) but depending on the length of the execution they could complete out of order. (i.e. the second task could finish before the first)"

Hence -> No ordered execution of events if they depend on the result of the others, if your processing subscription algorithm isn't 100% parallelizable you are out of luck.

 

Well, actually it's why I've implemented the Mutex extension 😉 

 

Best Regards

B
BABA-SHYAM15-Moonstone
15-Moonstone
June 9, 2020

Hi,

 

Subscription work in async mode. That means if you are calling one service and 100 of calls has triggered the subscription than multiple threads will be created and the service will called by 3-4 threads within the process.

There can be changes where you want to create Things using subscription, then there are chances 3-4 threads start accessing same thing which might be in process of creation which will lead some more issue. Better if you want to create any entity use for loop.

 

Regards

Shyam

Terms & ConditionsAccessibility statement