[
https://issues.apache.org/jira/browse/HBASE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607630#action_12607630
]
stack commented on HBASE-700:
-----------------------------
LN: We could do it that way. Downside is that it would introduce a second
location for table/column configs. apart table descriptor
Andrew: All sounds great. Doing all in hbase-42 sounds good (rather than as a
new issue). I like your description of how the read-only would work.
> hbase.io.index.interval need be configuratable in column family
> ----------------------------------------------------------------
>
> Key: HBASE-700
> URL: https://issues.apache.org/jira/browse/HBASE-700
> Project: Hadoop HBase
> Issue Type: Improvement
> Components: regionserver
> Affects Versions: 0.1.2
> Reporter: LN
> Priority: Minor
>
> setting parameter hbase.io.index.interval to smaller can improve hbase
> reading performance significantly, esp. in large value size column families.
> however, small hbase.io.index.interval cause more memory usage, because all
> index will read into memory when loading a mapfile.
> in my test env, i set hbase.io.index.interval to 1, after inserting about 3M
> samll size records to a table(about 1.5G in hadoop file), the regionserver
> throws OOME. then i found total size of map file index is 350M. however,
> i can't adjust hbase.io.index.interval to a larger one, like 32, because
> other big cell size tables need it be 1.
> so, i think make hbase.io.index.interval a column family property should be
> very important for performance tuning.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
