Re: Profiling Java Stored Procedures
Date: Tue, 17 Mar 2015 10:28:54 +0000
Message-ID: <CAP=5zEi0HTO0KH=Lh9z173P=ehrpAzWxaetFezVCYfy9Dwd0RA_at_mail.gmail.com>
Hi.
Not an answer to your question, but you can natively compile stored Java, which might improve the performance of the non-data access portions of the code.
http://oracle-base.com/articles/9i/java-native-compilation-9i.php
It worked pretty well for some stuff I was doing on a previous project...
Is it possible it was natively compiled on one system and not the other?
Cheers
Tim...
On Tue, Mar 17, 2015 at 10:18 AM, Niall Litchfield
<niall.litchfield_at_gmail.com> wrote:
> Morning/Afternoon/Evening all
>
> We recently had a situation where a stored procedure was performing slowly
> in one environment but quickly in a second. Naturally the dba looking at
> this issue traced the session, only to discover that the time was all
> attributed to an exec call for a stored procedure. It turns out that this
> stored procedure is in fact a java stored procedure.
>
> Is it possible to profile the execution of java stored procedures in the
> same way that one can profile a pl/sql procedure. The documentation suggests
> that it probably is, if the java class was compiled with debug information
> (it probably wasn't).
>
> Even better are there any reliable examples of this on the web that I could
> look at.
>
> FWIW this particular piece of code does some CPU intensive work that doesn't
> modify data, so the choice of a JSP looks reasonable.
>
> --
> Niall Litchfield
> Oracle DBA
> http://www.orawin.info
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Mar 17 2015 - 11:28:54 CET