After you tune PAS for OpenEdge client requests, you can begin tuning the OpenEdge web applications and MS Agent processes to achieve the following goals:

  • Control the size of the ABL session pool in the Session Manager
  • Manage resource consumption within an MS Agent process
  • Manage concurrent ABL request execution
  • Manage PAS for OpenEdge startup time

The design and implementation of your ABL application affects the PAS for OpenEdge instance and all web applications deployed on it. In most cases the ABL application design and implementation should not be changed. Your goal is to strike a balance between PAS for OpenEdge instance startup times, supporting client requests to your ABL business logic, and the response time to those clients.

One of the realities in getting the most performance from your PAS for OpenEdge instance is that the OpenEdge web applications and the MS Agent process execution of client requests is gated by your tuning the instance in which they operate. For example, it does not matter if you configure OpenEdge to handle 400 concurrent client requests if the instance it runs in can support only 200 concurrent client requests.

Another reality is that the execution speed of the ABL language engine and the OpenEdge RDBMS storage engine are tied to the speed of the OS, the CPUs, and the file system, but not to the PAS for OpenEdge instance.