Re: performance problems with classpath 0.09 on Jikes RVM

[David P Grove]

Here's some more data:  dynamic
count of JNI functions executed in 1 iteration of jack size 100 on classpath
0.08 and classpath 0.09 with Jikes RVM. Note the massive number of calls
from FileChannelImpl.get_native_fd 2/3 of which are unnecessary.  Unless
I hear that someone else has already fixed it, I'll put a patch together
in the next couple of days.

--dave

address@hidden SPECjvm98]$ cat jack.trace.0.08
| grep JNI | sort | uniq -c | sort -nr
  10017 JNI called: GetByteArrayElements
  10017 JNI called: ReleaseByteArrayElements
    408 JNI called: ReleaseStringUTFChars
    408 JNI called: GetStringUTFChars
      6 JNI CallXXXMethod:
 (mid 7653) java.lang.Double.isNaN
      6 JNI called: NewStringUTF
      6 JNI called: CallStaticBooleanMethod
      5 JNI called: GetStaticFieldID
      3 JNI called: SetLongField
      3 JNI called: GetStaticObjectField
      3 JNI called: ExceptionOccurred
      2 JNI called: GetStaticDoubleField
      1 JNI called: GetStaticMethodID
      1 JNI called: GetFieldID

address@hidden SPECjvm98]$ cat jack.trace.0.09
| grep JNI | sort | uniq -c | sort -nr
 301590 JNI called: GetIntField
 301590 JNI called: GetFieldID
 301590 JNI called: FindClass
  10388 JNI called: GetByteArrayElements
  10388 JNI called: ReleaseByteArrayElements
    408 JNI called: ReleaseStringUTFChars
    408 JNI called: GetStringUTFChars
      6 JNI CallXXXMethod:
 (mid 5333) java.lang.Double.isNaN
      6 JNI called: NewStringUTF
      6 JNI called: CallStaticBooleanMethod
      5 JNI called: GetStaticFieldID
      3 JNI called: SetStaticObjectField
      3 JNI called: NewObject
      3 JNI called: ExceptionOccurred
      2 JNI called: GetStaticDoubleField
      1 JNI called: GetStaticMethodID
      1 JNI called: GetMethodID