Some ideas: - Are you using transactions in the correct way? - If you were on Oracle you'd probably don't want to use SimpleDatasource (because of rollbacks) - Is your ping query setup correctly? - Are you using parameter binding with your JDBC? - Are you executing the same query (iBATIS/JDBC) using the same user-id?
Regards, Sven > >3-5 times slower does not sound correct. I would be curious to hear >how you setup and administered these tests. > >Brandon > >On 2/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> >> Sven, >> >> thanks for your response. I did some preliminary test on iBATIS' >> performance. For JDBC (MySql 5.0), i recorded time from establishing >> connection, result set, and mapping the result to objects. For list of >> simple objects, it seems to me that iBATIS (no caching and lazyloading) is >> 3-5 times slower than using JDBC. Of course, i believe my xml mapping has >> room to improve. >> >> The reason I asked is that I need some stats to persuade myself and >> coworkers to accept iBATIS as a data persistence tool for our relatively >> heavily loaded servers. >> >> btw, we just pushed a project using iBATIS to QE. For that project, >> performance is not big issue. >> >> Thanks, >> Tony > >
