[
https://issues.apache.org/jira/browse/HDDS-14166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swaminathan Balachandran updated HDDS-14166:
--------------------------------------------
Description:
Completely get rid of byte array operations for PUT and DELETE from
RDBBatchOperation. A direct byte buffer copy can be still performed even if a
byte array is sent from the table interface. Since the underlying rocksdb
interface is going to perform the same buffer copy on the JNI side i.e. copying
heap to off heap memory. Thus it would be more optimal to just copy it to
direct byte buffer and get rid of the byte array for gc. This directByteBuffer
can be now used for ByteWise comparisons which would be much faster on the
native side done in HDDS-14238
P.S. this cannot be done for delete range yet as there is no direct byte buffer
api in rocksdb yet. This tries to address the issue
[https://github.com/facebook/rocksdb/pull/14197]
was:Completely get rid of byte array operations for PUT and DELETE from
RDBBatchOperation. A direct byte buffer copy can be still performed even if a
byte array is sent from the table interface. Since the underlying rocksdb
interface is going to perform the same buffer copy on the JNI side i.e. copying
heap to off heap memory. Thus it would be more optimal to just copy it to
direct byte buffer and get rid of the byte array for gc. This directByteBuffer
can be now used for ByteWise comparisons which would be much faster on the
native side done in HDDS-14238
> Completely get rid of byte array operations from RDBBatchOperation
> ------------------------------------------------------------------
>
> Key: HDDS-14166
> URL: https://issues.apache.org/jira/browse/HDDS-14166
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Swaminathan Balachandran
> Assignee: Swaminathan Balachandran
> Priority: Major
> Labels: pull-request-available
>
> Completely get rid of byte array operations for PUT and DELETE from
> RDBBatchOperation. A direct byte buffer copy can be still performed even if a
> byte array is sent from the table interface. Since the underlying rocksdb
> interface is going to perform the same buffer copy on the JNI side i.e.
> copying heap to off heap memory. Thus it would be more optimal to just copy
> it to direct byte buffer and get rid of the byte array for gc. This
> directByteBuffer can be now used for ByteWise comparisons which would be much
> faster on the native side done in HDDS-14238
> P.S. this cannot be done for delete range yet as there is no direct byte
> buffer api in rocksdb yet. This tries to address the issue
> [https://github.com/facebook/rocksdb/pull/14197]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
