Folks
Appreciate your experience here.
Currently, we are running on I.S. 6.0.1 SP2.
We have defined 1 single JDBC Pool Alias (Mix conn 20 / Max 80) for ISCoreAudit, ProcessAudit, XRef, TN.
One of our new architect suggests that we should define 4 seperate
JDBC Pool Aliases (still pointing to the same Oracle Database Instance/Schema though) with connection Min 5 / Max 20, and suggests that it should result in noticeable performance improvement, based on his pervious experience.
However, my understanding of JDBC Connection Pooling suggests otherwise (i.e there should not be any noticeable performance improvement, if there is any at all).
My theory is that the only ‘contention’ with 1 ‘large’ connection pool versus 4 ‘small’ connecion pool is that all 4 threads (ISCoreAudit, ProcessAudit, TN and XRef) will / may try to access the in-memory synchronized Java Object - Connection Pool Object at the same time to get connection (where the most expensive operation should be establishing DB connection, and all these DB connection should have been established). This Java Object ‘contention’ should be unnoticeable at all (talking about ms ), if there is any.
Can anyone share his/her experience here ! Thank in advance ! My question is what is the performance difference with 1 conection pool (with higher maximum number of connection) vs 4 connection pools (with
lower maximum number of connection) for ISCoreAudit, ProcessAudit, XRef and TN
In addition, the archtect also suggest that we migrate all application from WmDb to JDBC Adapater (which I totally agree). But I would like to know, since both WmDB and JDBC Adapter are using the same JDBC Driver, what kind of improvement (performances, connection management, memory, etc) does JDBC Adapter by itself brings to the table (remember, same JDBC DataBase Drivers). The architect suggests that the migration should be treated as high priority (which I disagree on this point).
However, I do agree we have to migrate the application since WmDB may be deprecated in future webMethods releases.
Once again, appreciate your experience here.