M
Michael Jacobs
Guest
The agentStartupProc & agentStartupParam is used to do some one-time OS level initialization for Agent OS process. So your DB and all other ABL session startup options should go in the agentStartupParams, which is delivered to each ABL session started in the Agent. In a production server the number of ABL sessions present in any one Agent is increased automatically from numInitialSessions when a new client request is received and all of the existing ABL sessions are busy executing other client requests. Yes the development version of PAS for OE is limited to 5 concurrent client requests - where all 5 must run in the same Agent. So we limit the number of Agent processes to one and eliminate confusion and complexity. The production version has no limits on the number of ABL sessions that may be spread across one or more Agent processes. The indicators so far has shown that a single Agent process is generally sufficient for the old Stateless or State-free application models, but it REALLY depends upon how the ABL application is written. maxConnectionsPerAgent ... That controls the number of concurrently running client requests an one Agent process can execute. Each actively executing client request runs in a separate OS thread. numInitialSessions indicates how many ABL sessions will be pre-started when an Agent OS process is started. After all of the ABL sessions have been started the PAS for OE server is then ready to service incoming client requests. Production PAS for OE servers will automatically scale the number of Agent processes, up to the maximum number, when all of the existing Agents are engaged in actively running the maximum # of concurrent client requests. Does this help? Mike J. From: dziugasj bounce-dziugasj@community.progress.com Reply-To: " TU.OE.Development@community.progress.com " TU.OE.Development@community.progress.com Date: Wednesday, April 29, 2015 at 5:27 AM To: " TU.OE.Development@community.progress.com " TU.OE.Development@community.progress.com Subject: [Technical Users - OE Development] Pacific parameters for performance tunning Pacific parameters for performance tunning Thread created by dziugasj For one Pacfic instance (for example oepas1) we have one Session manager, one MS Agent which controls numerous ABL sessions. Can please anybody explain Pacific parameters from openedge.properties: [AppServer.SessMgr] agentStartupParam -- connection to the db is made here maxABLSessionsPerAgent =200 -- When number of Sessions is increased ? I always get initial number from numInitialSessions maxAgents =10 -- For Pacific development version MS Agent is always one ? maxConnectionsPerAgent =50 -- Do not understand this parameter and how to tune it, description from README does not help. numInitialAgents =1 [AppServer.Agent] numInitialSessions =50 -- Number of Sessions per MS Agent. This parameter determine how many DB connections are made P.S. What for several MS agents are needed if we have a lot of sessions ? Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
Continue reading...