[ https://issues.apache.org/jira/browse/HBASE-23296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17120804#comment-17120804 ]
Guanghao Zhang edited comment on HBASE-23296 at 6/1/20, 7:44 AM: ----------------------------------------------------------------- {quote}yes, we need a bigger L1, it's not suitable to keep it on the heap {quote} So use offheap as L1 and file as L2? Why don't use bigger heap as L1, because gc problem? was (Author: zghaobac): {quote}yes, we need a bigger L1, it's not suitable to keep it on the heap {quote} So use offheap as L1 and file as L2? Why don't use heap as L1, because gc problem? > Add CompositeBucketCache to support tiered BC > --------------------------------------------- > > Key: HBASE-23296 > URL: https://issues.apache.org/jira/browse/HBASE-23296 > Project: HBase > Issue Type: New Feature > Components: BlockCache > Reporter: chenxu > Assignee: chenxu > Priority: Major > > LruBlockCache is not suitable in the following scenarios: > (1) cache size too large (will take too much heap memory, and > evictBlocksByHfileName is not so efficient, as HBASE-23277 mentioned) > (2) block evicted frequently, especially cacheOnWrite & prefetchOnOpen are > enabled. > Since block‘s data is reclaimed by GC, this may affect GC performance. > So how about enabling a Bucket based L1 Cache. -- This message was sent by Atlassian Jira (v8.3.4#803005)