Hi Denis, > It's not obvious to me why this happened, so I think now I will put > this type of optimization aside and convert to JNI,
I've only followed your discussion with Jim but skipped all the in-depth discussion. >From my prior experiences usually JNI is not woth the trouble, if you don't have a serious reason why using native code would have advantages (like the possibility of using SIMD or when value-types would be a huge benefit), it has its own performance pitfalls especially if the workload is small and things like Get*ArrayCritical cause scalability problems because they have to lock the GC. > where profiling > will be easier (for me - I haven't been able to make OProfile work > for java yet). Have you had a look at the Netbeans profiler? It supports sampling based testing to keep the influence of the profiler at a minimum. Thanks for working on this! - Clemens
