Using JDBC Connection pool for Netezza backed applications
Using Connection pool is normal for Java web applications or enterprise applications. In case of a web application whose reporting is backed by Netezza, is it a good idea to use Connection Pool? definitely, but the connection pool size should be choosen rationally. As per Netezza docs or forums an appliance support 42 concurrent connections. So as per my experience the application should hold the connection pool which is reasonably half of this size, so that the other connections would be reserved for data loading etc. In our case we used an open source connection pool c3p0 and it was very effective to serve the purpose. After introducing the connection pool in our application the processing time for a job generating reports was cut down by 30%.
















