Re: Confirming on parameterMap versus ParameterClass

[Larry Meadors <la...@gmail.com>]

I think I wrote that part and that it is wrong. :-/

A better description of the performance is this:

If you define a parameter map, the time to build the parameter map is
taken at startup. If you don't define a parameter map, the time to
build the parameter map is taken on the *first call* to the mapped
statement that uses it.

The first call to a mapped statement without a parameter map would
incur a small delay as the parameter map is built. After that, it
would be identical to a mapped statement with a parameter map defined.

So, if you have a lot of parameter maps, you may actually experience a
slight performance boost at startup by removing them, then as the
application gets used, you'll see a tiny delay the *first time* a
mapped statement is called as that work is done then. In either case,
it's only done once.

Larry

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
For additional commands, e-mail: user-java-help@ibatis.apache.org