I found a very important in the connection pool: max_statements Certain connection pools, drivers, databases, and other portions of the system may provide an additional cache system, known as a statement cache. This cache stores a partially compiled version of a statement in order to increase performance. By reusing the parsed or precompiled statement, the application is able to trade an increase in memory usage for a boost in performance.
Example: <property name="hibernate.c3p0.min_size">2</property> | <property name="hibernate.c3p0.max_size">10</property> | <property name="hibernate.c3p0.timeout">5000</property> | <property name="hibernate.c3p0.max_statements">100</property> | <property name="hibernate.c3p0.idle_test_period">300</property> | <property name="hibernate.c3p0.acquire_increment">2</property> My average time to retrieve data is now divided by a factor of 5!!! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3913600#3913600 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3913600 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
