Apama 10.15.0 | Developing Apama Applications | Developing Apama Applications in EPL | Defining Queries | Implementing parameterized queries | Scaling and performance of parameterized queries
 
Scaling and performance of parameterized queries
Depending on the machine architecture a user can expect to be able to create several hundred parameterizations, which all concurrently process events.
As a result of the time required to process a parameterization edit request, the recommendation is to avoid multiple simultaneous edit requests for the same parameterization. There is no guarantee that all of the threads executing the parameterization will hold the same parameter values during the update period. During the update period, there might be a mix of results based on old parameter values and results based on new parameter values. Any requests to the same parameterization should be spaced approximately 1 second apart to allow time for requests to be executed throughout the parameterization. This applies to create, edit and delete requests.
In a cluster of correlators, the correlators share the same set of parameter values across the cluster. While a Scenario Service client can connect to any correlator in the cluster, it is not recommended to edit the same parameterization from multiple Scenario Service clients concurrently, as the results will be undefined.