JPype optimization notice

@ctrueden,

It has been a while since I last touched base here. I just wanted to tell you that JPype is working through a fairly massive speed upgrade. While I don't think that I busted any conversion paths in process, pyimagej is certainly one that is likely to stress the new paths. Typical speed up was between $1.5\times$ to $10.\times$ depending on the code path with buffer transfer of multidimensional arrays being the main target. We have a large backup of PR so not sure when this will actually land. PyImageJ actually got used by one of my projects recently, so keep up the good work!

https://github.com/jpype-project/jpype/pull/1470
https://github.com/Thrameos/jpype/blob/array-transfer-phase3/project/benchmark/RESULTS.md

Read JPype pull request #1470 and the benchmark results in project/benchmark/RESULTS.md first, then consider how the reported conversion and multidimensional-array changes affect pyimagej. The issue names no pyimagej file, test, requested change, or completion condition.

Written by the indexing model from the issue text.