Hoi,
for testing Oracle JDBC responsetimes of "not-very-short" running queries I
recognized, that the size of the resultset (i.e. number of records) impacts
the measured time somehow exponentially when exceeding e.g. 1000 records.
Example:
Query X with a result of 1000 records needs 2 seconds
Query X with a result of 2000 records needs 4 seconds
Query X with a result of 4000 records needs 15 seconds etc.
During the test, I recognized one CPU (Core) beeing completely used by
JMeter while the network connection shows almost no traffic and the Oracle
DB only shows waits for the client ("SQL*Net message from client") which
usually indicates that Oracle waits for the client gathering availiable
results.
For comparison I executed the same queries manually (via sqldeveloper also
using the same JDBC driver and a fetchsize of 5000) just fetching all
records and listing them. It took 1.8 seconds for 4000 records.
First I assumed that this may come from feeding the listeners and checking
contents in assertions but when I completely removed all listeners and
assertions from my JMeter testplan, the query with 4000 records still
required 15 seconds to finish.
Is there any way to overcome this overhead? I do not want to measure
Jmeter's overhead but only DB Query response time and JDBC resultset
fetching. I do not need assertions and can live with less features on this
sampler.
unfortunately, I can not simply reduce the size of my resultsets for various
reasons...
Thanks a lot in advance!
Regards
Peter
--
View this message in context:
http://www.nabble.com/JDBC-sampler-overhead-and-the-number-of-records-returned-tp24716684p24716684.html
Sent from the JMeter - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
