Optimum number of agents

[mobrien]

Hi All,

We have just moved to V10.2A.

Previously we had been on V9.1D. When running on this we had 22 Agents set up (due to our licensing). We are starting to get a lot more users using our system so we sometimes had issues with performance when there was a lot of users on.

I am led to believe that in V10 you are unlimited to the number of agents you can set up.

Is this correct? If so, is their an optimum/maximum number you should use?

Thanks

 

[Casper]

Hi All,

We have just moved to V10.2A.

Previously we had been on V9.1D. When running on this we had 22 Agents set up (due to our licensing). We are starting to get a lot more users using our system so we sometimes had issues with performance when there was a lot of users on.

I am led to believe that in V10 you are unlimited to the number of agents you can set up.

Is this correct? If so, is their an optimum/maximum number you should use?

Thanks

Well, I wonder how many users you serve then. I think 22 agents is very high. Assuming that you can serve 10-20 request per second per agent. That will mean that that you can serve ~250 requests per second. That is a pretty busy web application. There is no optimum number for the agents, you must however take in mind that one agent takes up about 30MB of memory. So right now you are already using ~650 MB of memory just for the agents.

Coming to your question how many agents you may start: With webspeed there is a very difuse and unclear licensing model, due to the fact that named users are most times undefinable, so that is something you really have to work out with your salesrep @Progress.

Regards,

Casper.

 

[mobrien]

Hi Casper,

Thank you for your response. During busy times we will have a maximum of 150 users on doing various things so this would suggest that there is a bigger problem than the number of agents.

If we have a process that takes a while (i.e. someone running a report or viewing a list of jobs) would this tie the agent up until the process is complete?

Thanks again for your help.

 

[Casper]

Hi Casper,

If we have a process that takes a while (i.e. someone running a report or viewing a list of jobs) would this tie the agent up until the process is complete?

yes, unless you split it of as a batchjob... Most times I see this many appservers running then it is because of running reports and other long running programs.
IMO the appserver should be used for short communication with the database and any potential long running program should be run as a separate session. (e.g _proges -b).

Casper.

 

[mobrien]

Hi Casper,

I think that will be the problem we are having. To many users running processes that take a while.

Thanks for the help and advice!

 

[yoachan]

yes, unless you split it of as a batchjob... Most times I see this many appservers running then it is because of running reports and other long running programs.
IMO the appserver should be used for short communication with the database and any potential long running program should be run as a separate session. (e.g _proges -b).

Casper.

run as a separate session. (e.g _proges -b)
Can you please tell me more about this? I'm having the same problem here....