hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vivek Ratan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-1974) Progress node should cache root object for faster progress computation
Date Wed, 03 Oct 2007 03:55:50 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vivek Ratan updated HADOOP-1974:
--------------------------------

    Attachment: 1974_patch02

In my earlier patch, I had forgotten to use just the relative path to the files. That has
been fixed in this patch (1974_patch02). 

> Progress node should cache root object for faster progress computation
> ----------------------------------------------------------------------
>
>                 Key: HADOOP-1974
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1974
>             Project: Hadoop
>          Issue Type: Improvement
>            Reporter: Vivek Ratan
>            Assignee: Vivek Ratan
>            Priority: Minor
>         Attachments: 1974_patch01, 1974_patch02
>
>
> In org.apache.hadoop.util.Progress.get(), we walk through the tree of objects to find
the root of a node, before figuring out the progress. This approach is not optimized, especially
since get() is called frequently. Each Progressnode should cache its root object, and this
is easy to do since nodes do not change their parents. 
> Keeping track of the root node is also useful in synchronization issues. [see HADOOP-1970
for more details]. The root node can be used to synchronize the entire structure for methods
that need to traverse the tree in different directions and lock nodes along the way. 

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