hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5727) Faster, simpler id.hashCode() which does not allocate memory
Date Tue, 05 May 2009 19:08:30 GMT

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

Hudson commented on HADOOP-5727:
--------------------------------

Integrated in Hadoop-trunk #827 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/827/])
    . Simplify hashcode for ID types. Contributed by Shevek


> Faster, simpler id.hashCode() which does not allocate memory
> ------------------------------------------------------------
>
>                 Key: HADOOP-5727
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5727
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Shevek
>            Assignee: Shevek
>             Fix For: 0.21.0
>
>         Attachments: 00_id-noallocate.patch, 03_id-noallocate.patch, 5727-0.patch
>
>
> Integer.valueOf allocates memory if the integer is not in the object-cache, which is
the vast majority of cases for the task id. It is possible to compute the hash code of an
integer without going via the integer cache, and hence avoiding allocating memory.

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