|
OK...thanks....that's what I figured..
Edwin
----- Original Message -----
Sent: Saturday, September 30, 2006 10:31
AM
Subject: Re: NodeletParser.process
I love profiling tools.
Yes, your sample size
is too small, and you should skip the startup steps. It's ridiculous
otherwise. It's kind of like getting NASCAR drivers to start their
engines AFTER they get the green flag.
Clinton
On 9/29/06, Edwin
Lukaweski <[EMAIL PROTECTED]> wrote:
We are profiling all the performance, including
startup.
This method takes up 5% of the total time
to run the application. maybe it is because the sample data size is too
small.
Edwin
-----
Original Message -----
Sent:
Friday, September 29, 2006 1:48 PM
Subject:
RE: NodeletParser.process
That's when
iBATIS parses the (configuration) files of DAO and/or SQLMaps. In a proper
setup, this is done only once. Are you profiling startup performance or
general performance?
Niels
We are
running iBatis in USS, under z/OS, and have done some profiling on the
application.
There seems
to be a significantly large amout of time spent in the method
"com/ibatis/common/xml/NodeletParser.process".
Can anybody
give me hints as to what this little guy is doing and how to optimize
it?
|
