On 9/3/2010 6:03 AM, Denis Lila wrote:
the cost of the context switches into native and back for each path
segment dominate the performance of long paths.
I see. That makes sense.
It was something I was meaning to fix for a long time (when that code
was first written native code was so much faster than Java and the
native transition was quick - since then Hotspot came along, got a
lot better, and the native transitions got much, much slower).
Do you think this will still be worth it after removing flattening?
That depends on the performance differential after your de-flattening
fixes. Are both now relatively close in performance?
Either way I imagine that performance will improve if we reduce the
native interface transitions - it just may change in relative priority
if your new widener is less abusive towards it...
...jim
