[
https://issues.apache.org/jira/browse/HBASE-15338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168498#comment-15168498
]
Liu Shaohui commented on HBASE-15338:
-------------------------------------
[~anoop.hbase]
{quote}
During these tests, we can specify cache blocks as false in Scan/Get and
achieve what you want?
{quote}
Not actually. If we specify cache blocks as false, the index blocks and meta
blocks need to be read from the underlying file system for Scan/Get, which is
not consistent with actual state of the HBase cluster. Usually the index block
and meta block can be cached in BlockCache. What we want to test is the latency
in the bad case when data block is not in cache and need to be read from the
file system for get.
> Add a option to disable the data block cache for testing the performance of
> underlying file system
> --------------------------------------------------------------------------------------------------
>
> Key: HBASE-15338
> URL: https://issues.apache.org/jira/browse/HBASE-15338
> Project: HBase
> Issue Type: Improvement
> Components: integration tests
> Reporter: Liu Shaohui
> Assignee: Liu Shaohui
> Priority: Minor
> Attachments: HBASE-15338-trunk-v1.diff
>
>
> When testing and comparing the performance of different file systems(HDFS,
> Azure blob storage, AWS S3 and so on) for HBase, it's better to avoid the
> affect of the HBase BlockCache and get the actually random read latency when
> data block is read from underlying file system. (Usually, the index block and
> meta block should be cached in memory in the testing).
> So we add a option in CacheConfig to disable the data block cache.
> Suggestions are welcomed~ Thanks
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
