Under low load, 1/3 of a second makes no difference. Under how many concurent users before iBatis puls ahead?
.V
Brandon Goodin wrote:
Your metrics are generic. Is your JDBC and PL/SQL also translating results into Lists of objects? Also, make sure you execute the statement within ibatis more than once. When you run a select for the first time it caches the mapping to the object. The second time through things are cached and should perform better. The only exception to this would be if you have remapResults set to true. The rule here is to be specific and map everything so that iBatis only has to perform minimal reflection.
Brandon
On Apr 6, 2005 1:19 PM, rodrigo castillo <[EMAIL PROTECTED]> wrote:
I tested the perfomance between ibatis, jdbc, and pl/Sql where ibates is 5 times but slow that the previous ones. How Can i improve perfomance of ibatis?.
The query has 100 rows.
IBATIS: 265 ms. c=97 IBATIS: 281 ms. c=97 IBATIS: 265 ms. c=97 IBATIS: 296 ms. c=97 IBATIS: 311 ms. c=97 JDBC: 78 ms. c=97 JDBC: 94 ms. c=97 JDBC: 47 ms. c=97 JDBC: 62 ms. c=97 JDBC: 47 ms. c=97
PL/SQL: 78 ms. c=97 PL/SQL: 94 ms. c=97 PL/SQL: 109 ms. c=97 PL/SQL: 109 ms. c=97 PL/SQL: 93 ms. c=97 PL/SQL: 78 ms. c=97 PL/SQL: 78 ms. c=97
