Try OpenEdge Now
skip to main content
Application Migration and Development Guide
Application Development with PAS for OpenEdge : Design and Implementation Considerations : Primary performance considerations : Setting the number of multi-session agents, sessions, and connections
 
Setting the number of multi-session agents, sessions, and connections
For best performance, you must determine the optimal settings for the PAS for OpenEdge properties that control the number of multi-session agents, sessions, and client connections that a session manager manages:
*Initial number of multi-session age to start (AppServer.SessMgr.numInitialAgents property in openedge.properties)
*Maximum number of multi-session agents to start Instances (AppServer.SessMgr.maxAgents property in openedge.properties)
*Maximum ABL sessions per multi-session agent (AppServer.SessMgr.maxABLSessionsPerAgent in openedge.properties) o
*Maximum connections per multi-session agent (AppServer.SessMgr.maxConnectionsPerAgent in openedge.properties)
In general, you must consider the number of clients, the design of your application (including the application model), and the hardware resources that run your PAS for OpenEdge instance. At a minimum, follow these guidelines in setting these values:
*For a session-managed application — You must have one ABL session for each client that connects to the PAS for OpenEdge instance. That is, you need as many ABL sessions as clients that connect concurrently to the PAS for OpenEdge instance.
*For a session-free application — You can have one session work on requests for multiple clients. At a minimum, Progress Software Corp. recommends one server session for each CPU in the machine. You can expect each multi-session agent to handle requests from up to 20 PAS for OpenEdge clients (or more). This is your per-agent client load. You can then scale up the number of agents to support the required multiple of per-session client load to match your total PAS for OpenEdge client load. The per-session client load also depends on the length of time it takes to complete an average client request. The longer it takes for an session to complete session requests, the fewer sessions are supported by each session, and the more sessions you need to handle the total PAS for OpenEdge client load. Thus, the total number of clients required is very application specific.
For more information on setting the server pool parameters, see Progress Application Server for OpenEdge: Administration Guide OpenEdge Application Server: Administration.