GetPrimitiveArrayCritical vs GetByteArrayRegion: 140x slow-down using -Xcheck:jni and java.util.zip.DeflaterOutputStream (original) (raw)

Thomas Schatzl thomas.schatzl at oracle.com
Mon Mar 19 09:28:07 UTC 2018

Hi,

On Fri, 2018-03-16 at 17:19 +0000, Ian Rogers wrote:

Thanks Paul, very interesting.

On Fri, Mar 16, 2018 at 9:21 AM Paul Sandoz <paul.sandoz at oracle.com> wrote: > Hi Ian, Thomas, > > [...] > (This is also something we need to consider if we modify buffers to > support capacities larger than Integer.MAXVALUE. Also connects > with Project Panama.) > > If Thomas has not done so or does not plan to i can log an issue > for you. > That'd be great. I wonder if identifying more TTSP issues should also be a bug. Its interesting to observe that overlooking TTSP in C2 motivated the Unsafe.copyMemory change permitting a fresh TTSP issue. If TTSP is a 1st class issue then maybe we can deprecate JNI critical regions to support that effort :-)

Please log an issue. I am still a bit unsure what and how many issues should be filed.

@Ian: at bugreports.oracle.com everyone may file bug reports without the need for an account. It will take some time until they show up in Jira due to vetting, but if you have a good case, and can e.g. link to the mailing list, this should be painless.

Thanks, Thomas

More information about the hotspot-gc-dev mailing list