I'm using iBatis on my first project and love the
separation of the data access from my code.
However after implementing a few pages of my
application using it, I'm noticing a significant
performance cost to using iBatis.
For example, I have a simple query that returns 48
rows of 40 fields each. The query itself returns in a
fraction of a second in the SQL Query Analyzer,
however the unit test calling through iBatis takes
8-10 seconds to return the 48 objects.
My result map does not do any selects or fancy data
conversions. The query results map directly to
properties in the data class using all primative data
types (strings, ints, bools).
Is this performance hit normal and is there anything I
can do to improve it?
Thanks,
Shawn.
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
