You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2021/10/01 13:28:00 UTC

[jira] [Resolved] (HBASE-26305) Move NavigableSet add operation to writer thread in BucketCache

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

Duo Zhang resolved HBASE-26305.
-------------------------------
    Fix Version/s: 3.0.0-alpha-2
                   2.5.0
     Hadoop Flags: Reviewed
       Resolution: Fixed

Pushed to master and branch-2.

Thanks [~xytss123] for contributing and [~comnetwork] for reviewing.

> Move NavigableSet add operation to writer thread in BucketCache
> ---------------------------------------------------------------
>
>                 Key: HBASE-26305
>                 URL: https://issues.apache.org/jira/browse/HBASE-26305
>             Project: HBase
>          Issue Type: Improvement
>          Components: BucketCache, Performance
>            Reporter: Yutong Xiao
>            Assignee: Yutong Xiao
>            Priority: Minor
>             Fix For: 2.5.0, 3.0.0-alpha-2
>
>         Attachments: logn in WriterThreads.png, logn in cacheBlock.png
>
>
> We currently use a ConcurrentSkipList to store blocks by HFile in bucket cache. The average time complexity of the add function is O(logn). We can move this time costly to the writer threads to reduce the response latency of read requests. I have tested the time cost of function cacheBlock in BucketCache and attached the metrics screenshots.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)