[
https://issues.apache.org/jira/browse/KAFKA-13900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Nigro updated KAFKA-13900:
------------------------------------
Description:
Java 9 has added a new Checksum method that can makes uses of ByteBuffer(s)
(see [Java 9's
Checksum::update|https://docs.oracle.com/javase/9/docs/api/java/util/zip/Checksum.html#update-java.nio.ByteBuffer-]):
Kafka already provides specific support for Java 9's Cr32C, hence it makes
sense it's going to use the most optimized version of it for direct ByteBuffers
as well (read-only or not), instead of performing a byte-per-byte computation.
I'm aware that currently the client's Buffer pools aren't using direct
ByteBuffer, but having full support for it can open the door to future
interesting optimizations on it.
was:
Java 9 has added a new Checksum method that can makes uses of ByteBuffer(s)
(see [Java 9's
Checksum::update|https://docs.oracle.com/javase/9/docs/api/java/util/zip/Checksum.html#update-java.nio.ByteBuffer-]):]
kafka already provides specific support for Java 9's Cr32C, hence it makes
sense it's going to use the most optimized version of it, in case fed
ByteBuffer is direct (read-only or not), instead of performing a computation
byte-per-byte.
I'm aware that currently the client's Buffer pools aren't using direct
ByteBuffer, but having full support for it can open the door to future
interesting optimizations on it.
> Support Java 9 direct ByteBuffer Checksum methods
> -------------------------------------------------
>
> Key: KAFKA-13900
> URL: https://issues.apache.org/jira/browse/KAFKA-13900
> Project: Kafka
> Issue Type: Improvement
> Components: clients, core
> Affects Versions: 3.1.1
> Reporter: Francesco Nigro
> Priority: Minor
> Labels: performance, performance-benchmark
>
> Java 9 has added a new Checksum method that can makes uses of ByteBuffer(s)
> (see [Java 9's
> Checksum::update|https://docs.oracle.com/javase/9/docs/api/java/util/zip/Checksum.html#update-java.nio.ByteBuffer-]):
> Kafka already provides specific support for Java 9's Cr32C, hence it makes
> sense it's going to use the most optimized version of it for direct
> ByteBuffers as well (read-only or not), instead of performing a byte-per-byte
> computation.
>
> I'm aware that currently the client's Buffer pools aren't using direct
> ByteBuffer, but having full support for it can open the door to future
> interesting optimizations on it.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
