You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2009/04/29 00:37:30 UTC

[jira] Assigned: (HBASE-1355) [performance] Cache family maxversions; we were calculating on each access

     [ https://issues.apache.org/jira/browse/HBASE-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack reassigned HBASE-1355:
----------------------------

    Assignee: stack

> [performance] Cache family maxversions; we were calculating on each access
> --------------------------------------------------------------------------
>
>                 Key: HBASE-1355
>                 URL: https://issues.apache.org/jira/browse/HBASE-1355
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>             Fix For: 0.20.0
>
>         Attachments: 1355.patch
>
>
> Profiling I see we are calculating max versions each time:
> {code}
>       String value = getValue(HConstants.VERSIONS);
>       this.cachedMaxVersions = (value != null)?
>         Integer.valueOf(value).intValue(): DEFAULT_VERSIONS;
> {code}
> Caching it should improve things.  Seeing that its 10% of memory when writing and about 10% of CPU.  Reading its 10% of CPU according to profiler.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.