In releases prior to Corticon 5.5, Decision Service instances executed using Decision Service-level thread pools. When multiple Decision Services were executing on a Server, this could overload the server and cause poor performance.
Beginning with Corticon 5.5, Server-level thread pooling is implemented by default, and multiple Decision Services place their requests in a queue for processing. That allows the server to determine how many concurrent requests are to be processed at any one time. The Corticon Server uses built-in Java concurrent pooling mechanisms to control the number of concurrent executions.