On Wed, 9 Oct 2002, Tim Bunce wrote:
> I'd guess it's related to the connect.
> Try it with DBI_PROFILE=6.
Here's what I get:
DBI::Profile: 0.001111 seconds 0.18% (10 method calls) prof_test.pl
'' =>
'FETCH' =>
0.000051s / 2 = 0.000026s avg (first 0.000010s, min 0.000010s, max 0.000041s)
'STORE' =>
0.000047s / 2 = 0.000024s avg (first 0.000023s, min 0.000023s, max 0.000024s)
'connect' =>
0.000238s
'disconnect' =>
0.000037s
'disconnect_all' =>
0.000009s
'SELECT * FROM ?' =>
'execute' =>
0.000285s
'finish' =>
0.000060s
'prepare' =>
0.000384s
So it looks like a bunch of automatic calls are ending up in the profile.
There are no finish(), disconnect() or disconnect_all() calls in the
script but they end up in the profile regardless. Shouldn't they fall
under this clause in the DBI::Profile docs:
If the method call was invoked by the DBI or by a
driver then the call is currently ignored for
profiling because the time spent will be accounted for
by the original 'outermost' call.
Also, where are those FETCH() and STORE() calls coming from?
-sam
