You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Wei-Chiu Chuang (Jira)" <ji...@apache.org> on 2023/04/22 23:16:00 UTC

[jira] [Commented] (HDDS-8047) [hsync] PutBlock request has lots of redundant metadata

    [ https://issues.apache.org/jira/browse/HDDS-8047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715325#comment-17715325 ] 

Wei-Chiu Chuang commented on HDDS-8047:
---------------------------------------

ChenXi, thanks for the info!
I'd like to take a stab at this issue in the coming week. We're looking at this from a hsync()-centric perspective, and having this issue resolved is critical to hsync.

> [hsync] PutBlock request has lots of redundant metadata
> -------------------------------------------------------
>
>                 Key: HDDS-8047
>                 URL: https://issues.apache.org/jira/browse/HDDS-8047
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Wei-Chiu Chuang
>            Priority: Major
>         Attachments: hbase_rs.html, image-2023-04-19-15-11-23-576.png
>
>
> In a profile result, we found that the client PutBlock request has lots of redundancy, especially the BlockData structure. The data structure contains the metadata of every chunk in the block, which is not required because only the last two chunks matters.
> This is especially critical for small and frequent puts, such as hsync API called by HBase WAL files. We found that at least 60% of client CPU cycle during hsync call can be attributed to this problem, and potentially a huge impact to the latency.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org