hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6532) Path objects are heavy
Date Tue, 02 Feb 2010 20:40:28 GMT

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

Eli Collins commented on HADOOP-6532:
-------------------------------------

Path is essentially a thin wrapper around URI so we'll end up implementing the URI functionality
that we use (eg the constructor error checking, the normalize, resolve, etc functions) so
memory savings won't be the same as just making uri a string. Also there are quite a few callers
of Path#toUri which we'll need to convert if we want to prevent creating URI objects. Most
of them don't want a URI though so that shouldn't be hard. I'm +1 on removing the URI member
and making Path implement the needed URI functionality explicitly just want to point these
issues out.

> Path objects are heavy
> ----------------------
>
>                 Key: HADOOP-6532
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6532
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs
>            Reporter: Tsz Wo (Nicholas), SZE
>         Attachments: Fun.java
>
>
> Compared with java.lang.String, org.apache.hadoop.fs.Path is much heavier since it contains
URI.  The size of a Path is roughly 3 times of a String.  See some numbers in the comments.
> A major impact of decreasing Path size is allowing ls, archive, etc. on directories with
many files.

-- 
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