Issue and tracking information
Developer's time Estimated effort to fix (hours):
Developer's Actual time spent on fix (hours)
Issue reporter to provide a detailed description of the issue in the space below
Issue #450 asks for updates to Container Processes and Components to support concurrency and priority options.
Container Processes
Container Processes should have a field allowing users to specify if they want the process to be single-threaded (Non-ExF behavior) or multi-threaded (ExF behavior). The default selection for all new container processes or migrated container processes will be single-threaded.
If Multi-threaded (ExF) is selected, they can choose how many threads they want to be in their thread pool for that container process with a default of 1. 0 is not allowed. The maximum amount allowed is an unsigned 16 bit integer.
This will likely need an update to the Container Process in the meta-model.
Priorities and concurrency
For each component instance deployed, we will be able to specify a priority for the entire component (default 0). Additionally, for each interface on a component that the component provides an implementation for (think on_one_data or any other callback), there will be an option to specify a priority on them. Lastly, we will want the ability to specify a concurrency value for each component (default 1).
See ExFChanges.pdf for details.
Issue and tracking information
Developer's time Estimated effort to fix (hours):
Developer's Actual time spent on fix (hours)
Issue reporter to provide a detailed description of the issue in the space below
Issue #450 asks for updates to Container Processes and Components to support concurrency and priority options.
Container Processes
Container Processes should have a field allowing users to specify if they want the process to be single-threaded (Non-ExF behavior) or multi-threaded (ExF behavior). The default selection for all new container processes or migrated container processes will be single-threaded.
If Multi-threaded (ExF) is selected, they can choose how many threads they want to be in their thread pool for that container process with a default of 1. 0 is not allowed. The maximum amount allowed is an unsigned 16 bit integer.
This will likely need an update to the Container Process in the meta-model.
Priorities and concurrency
For each component instance deployed, we will be able to specify a priority for the entire component (default 0). Additionally, for each interface on a component that the component provides an implementation for (think on_one_data or any other callback), there will be an option to specify a priority on them. Lastly, we will want the ability to specify a concurrency value for each component (default 1).
See ExFChanges.pdf for details.