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

Arpit Agarwal updated HDDS-8047:
--------------------------------
    Description: 
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.

  was:
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.


> [hsync] Make Putblock performance acceptable
> --------------------------------------------
>
>                 Key: HDDS-8047
>                 URL: https://issues.apache.org/jira/browse/HDDS-8047
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Wei-Chiu Chuang
>            Assignee: Wei-Chiu Chuang
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: after_hdds_8047.html, 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to