[
https://issues.apache.org/jira/browse/HBASE-17353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16382572#comment-16382572
]
Hadoop QA commented on HBASE-17353:
-----------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 4s{color}
| {color:red} HBASE-17353 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.7.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-17353 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12844190/HBASE-17353.patch |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/11754/console |
| Powered by | Apache Yetus 0.7.0 http://yetus.apache.org |
This message was automatically generated.
> Cache famLen in OffheapKeyValue
> -------------------------------
>
> Key: HBASE-17353
> URL: https://issues.apache.org/jira/browse/HBASE-17353
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 2.0.0
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Priority: Minor
> Attachments: HBASE-17353.patch, OffheapKV famLen cost.png
>
>
> WE need to discuss here. Already we had a TODO here. But this comes again
> after offheap memstore is committed in trunk.
> Attaching a screenshot to show the impact. True that these changes won't have
> a direct impact on the final perf but at micro level they would have.
> In case of KeyValue it is just retrieving a byte from the byte[] (o(1)
> access).
> But here we need to access the memory to retrive that one byte though it is
> Unsafe based.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
