Re: Varying elasped times in parse

Hi Jon,
If the two statements you list have been issued in sequence, the first time, the table and column definition has probably not been in datadictionary cache, while the second time it is in dictionary cache, thus reducing parse time.
Assuming this is not the only statement being issued, the cache information will disappear later on, and you will see again increased parse times. If there is any way you could bind the value list to host variables, this wouldn't happen of course.

Hth,

Sybrand Bakker, Oracle DBA

nordby_at_my-dejanews.com wrote in message <7ebi01$lmt$1_at_nnrp1.dejanews.com>...
>Any clue why a sql statement that is identical in
>structure, yet inserting different values in a
>dynamic sql environment, would have such radically
>different elapsed times on the parse? This
>happens when a single client performs 10000 of
>these inserts - about 40 of them account for 20%
>of the elapsed time on the test.
>
>Thanks for any insight, Jon.

[example sniped]

>-----------== Posted via Deja News, The Discussion Network ==----------
>http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
>
Received on Mon Apr 05 1999 - 23:39:27 CDT