Scenario Threading
The Scenario Thread Engine decreases the time it takes to execute a Scenario Chain or Scenario Chain Set by simultaneously executing multiple Scenarios within a Scenario Chain or Scenario Chain Set across multiple threads.
Please note: The Scenario Thread Engine runs its threads in any order it chooses. Thus, only use the Scenario Thread Engine on Scenario Chains or Scenario Chain Sets, where the order in which Scenarios are executed is insignificant.
When To Use
It would be good to thread Scenarios that contain the SegmentDataCreatorReceiver because it is used on two or more segment files (often hundreds of segment files) that are then merged into a single heavily nested document. Here, the order in which the segment files are created is insignificant. The Scenario Thread Engine also checks for Merge Receivers and knows to execute a Merge Receiver only after all segment threads have been executed.
When Not to Use
It would not be a good idea to thread Scenarios that contain any SQLInsertReceiver. Here, the order in which Scenarios are executed is significant due to the referential integrity of the data being validated on each row insertion.
Command-Line Example Threading a Scenario Chain
Syntax: genrocket -r ScenarioChain.grs -threaded <# of threads>
Example: genrocket -r JSONScenarioChain.grs -threaded 10
Command-Line Example Threading a Scenario Chain Set
Syntax: genrocket -r ScenarioChainSet.grs –threaded <# of threads>
Example: genrocket -r EDI87PSceanrioChainSet.grs –threaded 15
Link:
https://genrocket.freshdesk.com/a/solutions/articles/19000128328
Search GenRocket Knowledge Base
Related Assets
What is the ScenarioThreadEngine?
The ScenarioThreadEngine is specifically designed to decrease the time it takes to execute a ScenarioChain or ScenarioChainSet by simultaneously executing multiple Scenarios within a ScenarioChain or ScenarioChainSet across multiple threads.
Read More