You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2017/06/30 10:46:00 UTC
[jira] [Updated] (HBASE-15493) Default ArrayList size may not be
optimal for Mutation
[ https://issues.apache.org/jira/browse/HBASE-15493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-15493:
--------------------------
Fix Version/s: (was: 2.0.0)
> Default ArrayList size may not be optimal for Mutation
> ------------------------------------------------------
>
> Key: HBASE-15493
> URL: https://issues.apache.org/jira/browse/HBASE-15493
> Project: HBase
> Issue Type: Improvement
> Components: Client, regionserver
> Affects Versions: 2.0.0
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Attachments: HBASE-15493-v1.patch, HBASE-15493-v2.patch
>
>
> {code}
> List<Cell> getCellList(byte[] family) {
> List<Cell> list = this.familyMap.get(family);
> if (list == null) {
> list = new ArrayList<Cell>();
> }
> return list;
> }
> {code}
> Creates list of size 10, this is up to 80 bytes per column family in mutation object.
> Suggested:
> {code}
> List<Cell> getCellList(byte[] family) {
> List<Cell> list = this.familyMap.get(family);
> if (list == null) {
> list = new ArrayList<Cell>(CELL_LIST_INITIAL_CAPACITY);
> }
> return list;
> }
> {code}
> CELL_LIST_INITIAL_CAPACITY = 2 in the patch, this is debatable. For mutation where every CF has 1 cell, this gives decent reduction in memory allocation rate in both client and server during write workload. ~2%, not a big number, but as I said, already, memory optimization will include many small steps.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)