https://bz.apache.org/bugzilla/show_bug.cgi?id=66050
--- Comment #7 from feng <[email protected]> --- To Felix Schumacher I've been too busy lately to reply to you. Thanks for your advice.The maintainers of the driver have confirmed the parsing problems. It seems they use static parsing object for all threads resultset. Since they fix this,the test performance is better.But it still have a big difference from our own tests using my own program. Then i read some code in ApacheJMeter_jdbc.jar,i found this in AbstractJDBCTestElement.class: if (resultSetMaxRows < 0) { while (rs.next()) { currentIterationIndex = processRow(rs, meta, sb, numColumns, jmvars, varNames, results, currentIterationIndex); } } else { while (currentIterationIndex < resultSetMaxRows && rs.next()) { currentIterationIndex = processRow(rs, meta, sb, numColumns, jmvars, varNames, results, currentIterationIndex); } } My understanding for these codes is : if i don't set the variable : resultSetMaxRows , jmeter will parse all datas in resultset. According to the manunal , i set the "Limit Resultset" to 10, which i can't be sure it's the parameter "resultSetMaxRows". But the results are good. The result met my requirement. I read the manunal , still i have some questions hope to be answered. First: Is the variable "Limit Resultset" means "resultSetMaxRows " in the code? Second question which is most concerned : For example, a query sql returns 1,000,000 rows. If i set the "Limit Resultset" to 10, will jmeter still got 1,000,000 rows from database server , but only show the first 10 rows. I want jmeter put pressure on database server , but don't want the parsing blocked the pressure. By the way , don't worry about the dolphindb jdbc driver, i have confirmed the driver won't limit the results , even if the total number of results is large. Hope for your reply. Thanks ! -- You are receiving this mail because: You are the assignee for the bug.
