Each project contains microflows that take a lot of processing power and are executed often. These microflows can negatively influence the performance of your application during peak usage. This module enables you to control the amount of these microflows that are executed at once by assigning them to queues.
Each of these queues can be configured to handle a subset of these microflows and you can also set a limit to the number of microflows each queue can execute at once. This allows you to control the maximum load put on your application during peak usage by these microflows while still ensuring all microflows will be executed eventually.
The queues use a FIFO approach (first-in, first-out) and will automatically restart themselves (and any microflows still left to execute) after a server restart.
Modules5 stars, based on 11 votes
5/5starsMust have. Good one and fundamental!
Nick van Wieren
5/5starsFor those wanting to know about the Affinity setting; it relates to Java Thread priority for which you can find info in this article I found: http://www.geeksforgeeks.org/java-thread-priority-multithreading/
5/5starsGreat module. Essential to any project. Here are just some of the reasons why I like it
* If your application crashes while executing the scheduled microflow, it will be re-run automatically when the application is restarted.
* You can specify exactly how many threads you want to dedicate to the Queue
* Instead of referencing the microflow by its name in your code you can give it a friendlier process name.