Is Castor JDO using any connection pooling mechanism to improve the overall performance?
No, Castor JDO doesn’t have any built-in JDBC resource pooling. However the framework can transparently use any resource pooling facilities provided through DataSource implementation or -even better- through JDNI. In fact we even recommend people to use some Connection and PreparedStatement pool with Castor as this can increase Castor’s performance 3-5 fold. For example the following set of statements: db.begin(); db.execute(…) db.commit() will be executed in much less time with the resource pooling because it will avoid creating a new physical JDBC connection at every execution. With Oracle, instead of specifying the usual JDBC driver you can use a DataSource that specifically provides some Connection caching/pooling. Thus if your jdo config file looks like :
No, Castor JDO doesn’t have any built-in JDBC resource pooling. However the framework can transparently use any resource pooling facilities provided through DataSource implementation of -even better- through JDNI. In fact we even recommend people to use some Connection and PreparedStatement pool with Castor as this can increase Castor’s performance 3-5 fold. For example the following set of statements : db.begin(); db.execute(…) db.commit() will be executed in much less time with the resource pooling because it will avoid creating a new physical JDBC connection at every execution. With Oracle, instead of specifying the usual JDBC driver you can use a DataSource that specifically provides some Connection caching/pooling. Thus if your jdo config file looks like :
