The Mule execution engine is implemented on top of Project Reactor, providing the foundation for the non-blocking runtime. This implementation is a task-oriented execution model, where each operation inside a flow is a task that provides metadata about its execution, and the engine makes tuning decisions based on that metadata.
Mule Event processors indicate to the runtime what kind of work they do, which can be one of:
CPU Light: For quick operations, or Non-Blocking IO, for example, a Logger (
logger) or HTTP Request operation (
Blocking IO: For IO that blocks the calling thread, for example, a Database Select operation (
CPU Intensive: For CPU-bound computations, for example, through the Transform Message component (
See specific component or module documentation to learn the processing type it supports. If none is specified, the default is CPU Light.
For connectors created with the Mule SDK, the SDK determines the most appropriate processing type based on how the connector is implemented. For details on that mechanism, refer to the Mule SDK documentation.
Based on the processing type of a component, the runtime executes that component on a thread pool that is specifically tuned for that kind of work. These thread pools are managed by the runtime and shared across all apps in the same runtime. When started, the runtime introspects the available resources (such as memory and CPU cores) in the system to tune thread pools automatically for the environment where it is running. The default configuration was established through performance testing, which found optimal values for most scenarios.
The different thread pools allow the runtime to be efficient, requiring significantly fewer threads (and their inherent memory footprint) to handle a given work load when compared to Mule 3.
Configuration of the pools is calculated based on the available resources (CPU and memory) of the system at startup. The default configuration is based on performance testing for the optimal values for most scenarios. The default configuration can be modified through
schedulers-conf (documentation for the configuration options is within the comments of this file.). However, reconfiguration is not recommended. Note that the configuration is global and affects the entire Mule Runtime instance. MuleSoft strongly recommendeds that you perform load and stress testing with all applications involved in real-life scenarios to validate any change in the threading configurations and to understand how the thread pools work in Mule 4.
Note: By design, it is not possible to change the thread pools configurations in CloudHub. Any changes in local configurations will not be valid to compare to CloudHub applications.
The key aspects of each thread pool are described in the next sections.
CPU Light is for a relatively small thread pool (2 threads per available core by default).
Apart from executing the
CPU_LIGHT processors, this pool performs the handoff
of the event between processors in the flow (including the routers) and the
response handling for non-blocking IO.
In an app, when throughput drops or becomes unresponsive, it might be due to some code
CPU Light thread pool. This can be quickly checked by taking a
thread dump of the runtime and looking for
BLOCKED or for
long-running processes in the
CPU Light threads.
CPU Intensive is also a small thread pool (2 threads per available core by default), but it provides a queue for accepting more tasks.
IO is an elastic thread pool that grows as needed.
Tasks running in this pool should spend most of their time
instead of doing CPU work, so they do not compete with the other pools.
Also, when a transaction is active (since many transaction managers require all
steps of a same transaction to be handled by the same thread), the
Apart from the three core thread pools, some other pools are created by the runtime or some standard uses in some connectors:
Flow ring-buffer: Performs the handoff between the source of a flow and the flow itself. There is one pool for each flow, each with as many threads as half of the available cores by default.
NIO Selectors: Enables non-blocking IO. Each connector can create as many as required.
Under heavy load, there is a case where the runtime has no resources
available to handle a specific event. This issue might occur because the
threads are all busy and cannot perform the handoff of the newly arrived event or
because the current flow’s
maxConcurrency has been exceeded already.
In that case, a message is logged about the condition:
Flow 'flowName' is unable to accept new events at this time. Also, the source of the flow is notified to perform any required actions.
The actions to perform on back-pressure are specific to each connector’s
source. For instance, an
http:listener might return a
503 error code, while
a message broker listener might provide the option to either wait for resources to
be available or drop the message. In some cases, a source might
disconnect from a remote system to avoid getting more data than it can process
and then reconnect once the server state is normalized.
See specific connector documentation for details on how connector sources handle back-pressure.