How to correctly set jbo.ampool.maxavailablesize and minavailablesize ?

Question

Hi all,
On performance tuning of our ADF BC application, during load test I notice from application server (10.1.3.3) console that :
Request Processing Time (seconds) 11.45
Requests per second 7.91
From the docs, it is recommended to set both jbo.ampool.maxavailablesize and minavailablesize to be mutiplication of the above values, i.e : 90.
We have about 12 application modules (AM) in the application, no nested one.
The question is :
1) Should I set maxavailablesize and minavailablesize of ALL the 12 application modules to be 90 ?
Or Should I set the values selectively based on which AMs mostly accessed by the application invoked by the user ?
2) After I change the maxavailablesize and minavailablesize to be 90, I notice that just after the OC4J start and no user access the application yet, the database already has 20-30 sessions opened, Is this normal ?
Thank you for your help,
xtanto

Answer 1

Can you be more specific about what docs are recommending this? I don't see why you would want the max available size and min available size to be the same thing, but I'd like to review what documentation you are referring to for context.
max pool size puts an upper limit on the number of AM's that can be created in that pool. If you hit this limit users wait until one of the existing instances is freed up.
max available size gives a desired maximum that the pool should shrink down to after a period of higher-than-expected load.
the min available size is the lowest number that the AM pool can shrink down to when the system is less loaded.
I'd need to see all of your pool parameters, understand if you're using JDBC datasource or URL connection, and understand whether you use jbo.doconnectionpooling= true or false to explain any given set of behavior.