hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13579) Avoid isCellTTLExpired() for NO-TAG cases
Date Tue, 05 May 2015 19:34:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-13579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14529118#comment-14529118
] 

stack commented on HBASE-13579:
-------------------------------

bq. Can you explain the rationale for this statement?

Minor, unquantified perf improvement. Didn't think 0.98 would be interested.



> Avoid isCellTTLExpired() for NO-TAG cases
> -----------------------------------------
>
>                 Key: HBASE-13579
>                 URL: https://issues.apache.org/jira/browse/HBASE-13579
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Scanners
>    Affects Versions: 2.0.0
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>         Attachments: HBASE-13579_1.patch, HBASE-13579_2.patch, HBASE-13579_KVExtension.patch,
HBASE-13579_branch-1.patch, HBASE-13579_storelevel.patch
>
>
> As observed in this JIRA's performance test, we are always calling the isCellTTLExpired()
for every cell and internally it is parsing the keyLength, valueLength() to get the tagsLength
after which we decide whether Cell level TTL is present are not.
> This JIRA aims to avoid this check if all the readers of the storescanner knows that
there are no tags to read.  Note that, for the memstore scanner we will do that in another
JIRA, which I suppose Stack had already raised to avoid tag length while flushing (for the
NO-TAG) case.



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

Mime
View raw message