Worklight v5.0.5 > Develop Worklight applications > Develop the server side of an Worklight application > The adapter XML File<loadConstraints> element of the adapter XML file
The <loadConstraints> element defines the maximum load that is exerted on a back-end application by setting the maximum number of concurrent requests that can be performed on the system.Worklight queues incoming service requests from Worklight applications. While the number of concurrent requests is below the maximum, Worklight forwards the requests to the back-end application according to their order in the queue. If the number of concurrent requests is above the maximum, Worklight waits until an already handled request is finished, before it services the next one in the queue. If a request waits in the queue for longer than the timeout configured in the procedure, Worklight removes it from the queue, and returns a Request Timed Out exception to the caller.
The <loadConstraints> element has the following attributes:
Attribute Description maxConcurrentConnectionsPerNode Maximum number of concurrent requests that can be performed per server node of the back-end application. For example, to have a four-node system serve 100 transactions per second, where average response time is 2 seconds, each node must be able to manage an average of 50 transactions per second (100 x 2 / 4). We set...
<loadConstraints maxConcurrentConnectionsPerNode="50" />
If you increase the value of this attribute, the back-end application needs more memory. To avoid memory issues do not set too high
For more information about how to size your back-end application, see:
- Scalability and Hardware Sizing (PDF)
- Hardware Calculator (XLS)
Parent The adapter XML File