Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 31 Oct 2013 15:41:22 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12676757.1383191882508.1271.1383234082103@arcas>
In-Reply-To: <JIRA.12676757.1383191882508@arcas>
References: <JIRA.12676757.1383191882508@arcas>
Subject: [jira] [Updated] (HBASE-9867) Save on array copies with a subclass
 of LiteralByteString
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack updated HBASE-9867:
-------------------------

    Attachment: 9867.txt

Retry

> Save on array copies with a subclass of LiteralByteString
> ---------------------------------------------------------
>
>                 Key: HBASE-9867
>                 URL: https://issues.apache.org/jira/browse/HBASE-9867
>             Project: HBase
>          Issue Type: Improvement
>          Components: Protobufs
>    Affects Versions: 0.96.0
>            Reporter: stack
>            Assignee: stack
>             Fix For: 0.98.0, 0.96.1
>
>         Attachments: 9867.txt, 9867.txt
>
>
> Any time we add a byte array to a protobuf, it'll copy the byte array.
> I was playing with the client and noticed how a bunch of CPU and copying was being done just to copy basic arrays doing pb construction.  I started to look at ByteString and then remembered a class Benoit sent me a while back that I did not understand from his new AsyncHBase.  After looking in ByteString it made now sense.  So, rather than copy byte arrays everywhere, do a version of a ByteString that instead wraps the array.


--
This message was sent by Atlassian JIRA
(v6.1#6144)