[
https://issues.apache.org/jira/browse/HBASE-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674294#action_12674294
]
Erik Holstad commented on HBASE-80:
-----------------------------------
Was thinking that it is not really clear to me how the new setup where a Class
is aware of it size,
implementing HeapSize, is going to be used for the rest of the project. So I
propose that for now
have 2 different versions of Cell and HbaseMapWritable, one that keeps track of
the size and one
that doesn't, so the overhead of keeping the size doesn't slow down other use
cases.
Another question is also where and when to do the calculation of the size, I
have chosen to put
it in the puts, adds and removes because I think that it is going to be read
many scenario for these
object.
> [hbase] Add a cache of 'hot' cells
> ----------------------------------
>
> Key: HBASE-80
> URL: https://issues.apache.org/jira/browse/HBASE-80
> Project: Hadoop HBase
> Issue Type: Improvement
> Components: regionserver
> Reporter: stack
> Assignee: Erik Holstad
> Priority: Minor
> Fix For: 0.20.0
>
> Attachments: cache.patch, Cell.java, hbase-80-v1.patch,
> HeapSize.java, LruHashMap.java, LruHashMapTester.java, MemoryTester.java,
> WR_PE.java
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
