jmeter-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 60382] DBCP2 - JDBC Sample became very slow since 3.0
Date Sat, 19 Nov 2016 13:25:35 GMT

--- Comment #5 from Felix Schumacher <> ---
Created attachment 34460
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
/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

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.
View raw message