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-14020) Unsafe based optimized write in ByteBufferOutputStream
Date Sun, 05 Jul 2015 20:25:04 GMT

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

stack commented on HBASE-14020:

This does seem like perfect jmh candidate though (I like the way your jmh findings are bourne
out (sp?) by PE test runs, at least to date).  What kind of PE was it [~anoop.hbase]

> Unsafe based optimized write in ByteBufferOutputStream
> ------------------------------------------------------
>                 Key: HBASE-14020
>                 URL: https://issues.apache.org/jira/browse/HBASE-14020
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Scanners
>            Reporter: Anoop Sam John
>            Assignee: Anoop Sam John
>             Fix For: 2.0.0
>         Attachments: HBASE-14020.patch, HBASE-14020_v2.patch, HBASE-14020_v3.patch
> We use this class to build the cellblock at RPC layer. The write operation is doing puts
to java ByteBuffer which is having lot of overhead. Instead we can do Unsafe based copy to
buffer operation.

This message was sent by Atlassian JIRA

View raw message