> All,
>
[quoted text clipped - 13 lines]
>
> Jaj
Applications and their various threads consume CPU resources, not DLLs
or other such resources. So perfmon reports correctly that "java" is
consuming CPU.
Instead, what you want to look for is profiling of the application, so
that you can find out where it's spending its time. There are some
profiling facilities with Java, though whether they're useful when you
have JNI code involved I can't say.
= Steve =

Signature
Steve W. Jackson
Montgomery, Alabama
Oliver Wong - 26 Jan 2006 20:28 GMT
>> All,
>>
[quoted text clipped - 22 lines]
> profiling facilities with Java, though whether they're useful when you
> have JNI code involved I can't say.
If you can't find a profiling tool that works well with JNI, and decide
to write your own, Java 1.5 added something called JVMTI that may help out.
See http://java.sun.com/j2se/1.5.0/docs/guide/jvmti/
- Oliver
javabuddha@gmail.com - 26 Jan 2006 20:51 GMT
I looked at this a while back:
http://java.sun.com/developer/technicalArticles/Programming/HPROF.html
It suppose to give you both heap and CPU usage by class, but didn't
have the time to play with it yet.
Good luck,
Matt
jaj_developer@yahoo.co.uk - 30 Jan 2006 11:08 GMT