Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <422081272.1258604563370.JavaMail.jira@brutus>
Date: Thu, 19 Nov 2009 04:22:43 +0000 (UTC)
From: "Hong Tang (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-6381) WritableUtils::*VLong utilities
 should be available for byte arrays
In-Reply-To: <145114006.1258506339719.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-6381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779818#action_12779818 ] 

Hong Tang commented on HADOOP-6381:
-----------------------------------

bq. That's what WritableUtils::decodeVIntSize does.
That means you would have to decode the first byte of the vint twice.

bq. where the object instantiation cost was just too much, performance-wise. No?
How effective would JIT help eliminate the overhead of objects created and forgotten in a tight loop? This should be the kind of things that compilers are good at.


> WritableUtils::*VLong utilities should be available for byte arrays
> -------------------------------------------------------------------
>
>                 Key: HADOOP-6381
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6381
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: util
>            Reporter: Chris Douglas
>            Priority: Minor
>         Attachments: C6381-0.patch, C6381-1.patch, C6381-2.patch
>
>
> Particularly when working with raw bytes in Writables, it is often useful to have versions of the vint utility functions for byte arrays.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.