hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-13614) Avoid temp KeyOnlyKeyValue temp objects creations in read hot path
Date Fri, 19 Jun 2015 11:57:00 GMT

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

ramkrishna.s.vasudevan updated HBASE-13614:
-------------------------------------------
    Attachment: HBASE-13614.patch

Removes the local KVOnlyKV in the HFileReaderImpl and EncodedSeeker.  In all these cases the
scanner instances are per get or scan. So we could use the same instance KeyOnlyKV to set
the key part for comparisons in blockSeek or seekToblock cases.
Also removes unused code in Prefixtree.  With this and HBASE-13939 we avoid cases where we
create lot of KeyOnlyKeyValue in hot read path. 

> Avoid temp KeyOnlyKeyValue temp objects creations in read hot path
> ------------------------------------------------------------------
>
>                 Key: HBASE-13614
>                 URL: https://issues.apache.org/jira/browse/HBASE-13614
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Anoop Sam John
>            Assignee: ramkrishna.s.vasudevan
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: HBASE-13614.patch
>
>
> As part of HBASE-10800, move to new CellComparator, we are temp creating a Cell out of
byte[]s so that the Comparator can compare.  In read hot path, we can try minimize the object
creations. The parent Jira added some such cases, which we can solve.  This Jira will solve
all such cases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message