[
https://issues.apache.org/jira/browse/HBASE-15338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168556#comment-15168556
]
Liu Shaohui commented on HBASE-15338:
-------------------------------------
Thanks [~jingcheng...@intel.com]
{quote}
I meant just making cache on read in CacheConfig configurable (a false value
for cache on read) can work as well instead of add a new global switch.
{quote}
If we make cache on read in CacheConfig configurable and set it to false, the
index and meta blocks will not be cached. This is not what we expect. Of
course, we can update the meaning of this config by changing the code.
And the data block may also be cached if we set hbase.rs.cacheblocksonwrite to
be true.
> 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
> Fix For: 2.0.0
>
> 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)
