Re: Java stored procedure performance dilemma

On Thu, 17 Oct 2002, kyu_at_biodiscovery.com wrote:

> Billy's ending comments pretty much point to a plan of attack: SQL,
> PL/SQL, Java, C.
>
> Inmost cases, java programs are slow because the programmers don't
> know how to interact with the database. They fetch too much data to
> the JVM in too many trips, do little processing, and send the results
> back.
>
> Ask the programmers: the amount of data retrieved from the DBMS and is
> that necessary? The dumbest case is to retrieve prices, change them
> and send them back. That can be done with update product set price =
> price*0.8 where stockingDate < sysdate-30. the number of passes over
> the data?strive for single pass. profile the java program to find
> what step is taking the time.

There is a JVM within Oracle. You probably would have much less rework to compile your java routines as java database objects and then execute your code that way. With the round trips being this issue, this might be your quickest solution.

Search around on

http://asktom.oracle.com/pls/ask/
as well as
http://tahiti.oracle.com/

-- 
Galen deForest Boyer
Sweet dreams and flying machines in pieces on the ground.