https://bz.apache.org/bugzilla/show_bug.cgi?id=60382
Bug ID: 60382
Summary: DBCP2 - JDBC Sample became very slow since 3.0
Product: JMeter
Version: 3.0
Hardware: PC
Status: NEW
Severity: regression
Priority: P2
Component: Main
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Created attachment 34454
--> https://bz.apache.org/bugzilla/attachment.cgi?id=34454&action=edit
JMX file to benchmark insertion throughput of SQL Databases
Hi,
I update from JMeter 2.11 to JMeter 3.0 and faced issues with the JDBC Sampler.
I execute as many insertion queries as possible against different databases to
measure their throughput. Switching to JMeter 3 decreased the throughput by 2
on different databases.
For example, on H2, I had 7000 inserts/sec; now I'm around 3500 i/s.
In the bug 58786, there is a discussion about performance regression but the
patch has been merged, so I guess there is a workaround, but I didn't find it.
I attached a jmx file. You can notice that I set the poolMax to 1 instead of
10, but it does not solve the problem.
How can work around this issue?
Regards
--
You are receiving this mail because:
You are the assignee for the bug.
