Bryce McKinlay wrote: > By my (casual) measurements, our JNI is on the order of 10X slower > than the JRE for Java->C calls. There's a test case in bugzilla: >> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12957 >> But you're right, maybe we should oprofile it to be sure. Hans pointed me at qprof: http://www.hpl.hp.com/research/linux/qprof - Nice simple profiler thats a lot quicker to setup and use than oprofile. I've updated the bug report with the profiler output. It shows that about 90% of the test case's runtime is spent in _Jv_GetJNIEnvNewFrame and Malloc/Free - definately a case for optimization, I think. Regards Bryce.