Re: PL/SQL Optimisers

Terrence Wong wrote:
>
> Am interested to know also :
> (1) How to optimised the PL/SQL for the web environments.

Would the code be optimized differently for the web? If anyone has a "yes" response to this, I would be interested in seeing it.

> (2) Should I restrict the total size of the package, ie. spilting into
> multiple small packages.

When any part of a package is access, the entire package is read into the
SGA. If the package is large enough and the SGA is crowded enough, one or
more current residents could be evicted. *If* this presents a problem, you
can move large components that are rarely used to a separate package. No
sense loading rarely-used components until needed.

Assuming you have written well-modularize code, I wouldn't be breaking up
packages based strictly on raw size. Unless, of course, it becomes absolutly necessary. Nor would I set an arbitrary limit on the size of packages. A well-designed package will be as large or small as it needs to be.

> (3) How far can 'Explain Plan' or 'tkprof' accelerate the performance of
> the programs written for the web.

As far as you are able to use the output to better optimise your code!?! Again I am wondering how PL/SQL code would be different for a web-based app than, say, a "thin client" client/server app.

If there is a difference, then please CC me in the response as we will soon be moving to web-based apps ourselves.

> ... You could even answer in parts.

Whew!

-- 
Tomm Carr
--
"Can you describe your assailant?"
"No problem, Officer.  That's exactly what I was doing when he hit me!"