hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-1061) Memory footprint optimization for INodeFile object.
Date Wed, 24 Mar 2010 20:13:27 GMT

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

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

It appears that this proposal is:

 48 bits for preferredBlocksize (u.e. max block size is 512 TB)
 16 bits for block replication (i.e. max of 64000 replicas of a block)

This scheme should be backward compatible, no existing installations should have a problem
with these settings.  Seems like a good proposal to me.

> 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
>            Priority: Minor
>             Fix For: 0.22.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message