Database Reference
In-Depth Information
Figure 12-3.
Comparison of the database-side resource usage profile in test case 1 and test case 2.
(Components that account for less than 1% of the response time aren't displayed because they wouldn't be visible.)
Reusing Prepared Statements
I suggest in the previous section that using prepared statements is a very good thing. It's even better to reuse them
to eliminate not only the hard parses but the soft parses as well. Since in test case 2 the elapsed time for the parses is
almost not noticeable, you may ask yourself why. Before giving an answer, I show the performance figures related to
processing that reuses a single prepared statement. Specifically, Figure
12-4
shows a graphical representation of the
processing intended to improve on the performance in test case 2.
