I do not know what you have you tried, but my understanding of the 
bytecode cache is that it would basically just allow the JVM to 
short-circuit the JIT process on subsequent restarts of the JVM.  So the 
only difference you would see would be on subsequent invocations of your 
class files in a new JVM, and even then all you could observe would be 
that the JIT step would run faster.

In other words, I do not think there is much you can do to really see this 
effect unless you have some classes with long JIT times.  Also, I believe 
the JIT process doesn't even kick-in until your class/method has been used 
X number of times within a single JVM instance, so it may take some 
substantial usage before your class is even JIT compiled and you can take 
advantage of the bytecode cache.

Mark






"Raikov, Leonid" <RaikovL1@xxxxxxxxx>
Sent by: java400-l-bounces@xxxxxxxxxxxx
11/26/2003 12:44 PM
Please respond to Java Programming on and around the iSeries / AS400 
 
        To:     "'JAVA400-L@xxxxxxxxxxxx'" <JAVA400-L@xxxxxxxxxxxx>
        cc: 
        Subject:        Bytecode cache & WAS5.0


How can I find out whether ByteCode Cache File of WAS5.0 is indeed being
used by the server? I have configured it, but since there was no visible
improvement in the response times, I can't help wondering whether the
change has actually taken place.
 
Lo


_______________________________________________
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) 
mailing list
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.