On Tue, 10 Aug 2021 05:08:54 GMT, Sergey Bylokhov <[email protected]> wrote:
> This is the continuation of JDK-8233884 and JDK-8271456. This change affects
> fewer cases so I fix all "java." modules at once.
>
> In many places standard charsets are looked up via their names, for example:
> absolutePath.getBytes("UTF-8");
>
> This could be done more efficiently(up to x20 time faster) with use of
> java.nio.charset.StandardCharsets:
> absolutePath.getBytes(StandardCharsets.UTF_8);
>
> The later variant also makes the code cleaner, as it is known not to throw
> UnsupportedEncodingException in contrary to the former variant.
>
> tested by the tier1/tier2/tier3 tests on Linux/Windows/macOS.
Yes, while I don't know exactly which changes resolved JDK-6764325, it's clear
from the microbenchmarks added for #2102 that it's no longer an issue - at
least not in the mainline.
-------------
PR: https://git.openjdk.java.net/jdk/pull/5063
