Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <20071542.17281271050303576.JavaMail.jira@thor>
Date: Mon, 12 Apr 2010 01:31:43 -0400 (EDT)
From: "dhruba borthakur (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Commented: (HDFS-1061) Memory footprint optimization for
 INodeFile object.
In-Reply-To: <680844895.417801269297689033.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855843#action_12855843 ] 

dhruba borthakur commented on HDFS-1061:
----------------------------------------

we should try to get this into the impending 0.21 re-release. Can we fix the cause why  HadoopQA did a -1 to this one?

> Memory footprint optimization for INodeFile object. 
> ----------------------------------------------------
>
>                 Key: HDFS-1061
>                 URL: https://issues.apache.org/jira/browse/HDFS-1061
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>    Affects Versions: 0.22.0
>            Reporter: Bharath Mundlapudi
>            Assignee: Bharath Mundlapudi
>            Priority: Minor
>             Fix For: 0.22.0
>
>         Attachments: HDFS-1061.patch
>
>
> I am proposing a footprint optimization to merge blockReplication and preferredBlockSize fields into one 'long header' field in INodeFile class. This saves 8 bytes per INodeFile object on a 64 bit JVM. This memory optimization is transparent and changes are very minimal.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira