S
Satya Prasad
Guest
maxABLSessionsPerAgent=200 - This represents Maximum number of concurrent sessions an MS agent can spawn/start. maxAgents =10 -- For Pacific development version MS Agent is always one ? For Development, the limit is one though it configured as 10. maxConnectionsPerAgent=16 - I think, This represents Maximum number of concurrent connections an MS agent can have Thanks , Satya From: dziugasj [mailto:bounce-dziugasj@community.progress.com] Sent: Wednesday, April 29, 2015 2:57 PM To: 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...