How may one increase JVM/Java Stored Procedure Perfomance?

Question

Hi all,
my question: How can one increase the performance of the Oracle JVM, especially of Java Stored Procedures?
I ask this because I did some performance analysis (and was horrified :):
I have a static Java method that'll need an average 15 ms to return - when executed locally.
The same code, uploaded to an Oracle10g instance and published as Java Stored Procedure will take awful *925 ms*.
I measured both times from within the method as shown below:
public class JSProc {
public static void doSomething() {
long start = System.currentTimeMillis();
// now comes the '15 ms'-code
long time = System.currentTimeMillis() - start;
That way, I'm not including any call spec overhead, network communication or whatever into the 925 ms. All in all the above procedure call will take about 1200 to 1500 ms until it returns to the client...
The hardware: both client/server computers have the same hardware, both use the JDK provided with the latest Oracle10g release; single difference: client is Win2K, server is Linux.
I would be immensely grateful for your suggestions concerning the possibilities to increase the JVM performance...
Greetings,
Sam

Answer 1

As Avi suggested, subsequent calls of the procedure within the same session will reduce the execution time down to 40 ms in my testing environment.
But that doesn't change anything for the 'first call' - when I start a new client program that opens a new connection, the Java Stored Proc will again need about a second to return.
I wrote the procedure now in PL/SQL - it will return in less than 30 ms, subsequent calls will return in less than a ms. Guess what I'll use :)
I played around with the JAVA* configuration params, but, as expected, that doesn't change anything in terms of performance. According to documentation, it will only affect the amount of classes I can load into the server.
I just read that Oracle creates a new "little" JVM for every session, and I imagine that there's lot of method intercepting and things (the ominous AOP-code) to ensure transaction security.
That's why I come to the conclusion that I won't use Java Stored Procedures for classical "connect, execute, disconnect" client-server applications. It's like full braking on the freeway :)