https://bz.apache.org/bugzilla/show_bug.cgi?id=60382
--- Comment #5 from Felix Schumacher <[email protected]> --- Created attachment 34460 --> https://bz.apache.org/bugzilla/attachment.cgi?id=34460&action=edit Create sample data to be used with the testplan The testplan needs input data. I have guessed, what the data should look like and created a perl script, that generates that data (probably a bit too much). With that data and profiling with jmc (with oracle java 8) by using: export JVM_ARGS="-XX:+UnlockCommercialFeatures -XX:+FlightRecorder -XX:StartFlightRecording=duration=60s,filename=recordings_v2_13.jfr" /bin/jmeter -t /tmp/dbcp2-test/test-dbcp2.jmx -l /tmp/dbcp2-test/test-dbcp2_v3_1.jtl -j /tmp/dbcp2-test/test-dbcp2_v3_1.log -n -Jdb_url="jdbc:h2:mem:" -Jdb_class=org.h2.Driver -Jclient_data_dir=/tmp/dbcp-test2 I created a bit of profiling data and looking at it, saw that you are suffering from the removal of the prepared statement cache. H2 will spent 20% of the whole cpu cycles parsing the prepared statements. Modern jdbc driver should be able to cache those statements on their own. Are you using H2 in production as well? Could you test whether you have the same problems with your production db? -- You are receiving this mail because: You are the assignee for the bug.
