[ 
https://issues.apache.org/jira/browse/HDDS-17777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Soldatov resolved HDDS-17777.
------------------------------------
    Resolution: Won't Fix

> CodecBuffer allocates a new ByteBuffer view on every fill
> ---------------------------------------------------------
>
>                 Key: HDDS-17777
>                 URL: https://issues.apache.org/jira/browse/HDDS-17777
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: OM
>    Affects Versions: 2.2.2
>            Reporter: Sergey Soldatov
>            Assignee: Sergey Soldatov
>            Priority: Major
>
> CodecBuffer.put(ToIntFunction) and CodecBuffer.putFromSource call 
> buf.nioBuffer(index, length) every time they fill the buffer. Each call 
> creates a new DirectByteBuffer object.
> Many hot paths fill a CodecBuffer this way: RocksDB get, iterator key and 
> value reads, and string encoding. So OM operations that touch many entries, 
> such as key listing, create several short-lived ByteBuffer objects per entry. 
> This adds allocation and GC pressure on the OM.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to