hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5664) Use of ReentrantLock.lock() in MapOutputBuffer takes up too much cpu time
Date Fri, 29 May 2009 01:00:46 GMT

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

Chris Douglas updated HADOOP-5664:
----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.21.0
     Hadoop Flags: [Reviewed]
           Status: Resolved  (was: Patch Available)

I committed this.

> Use of ReentrantLock.lock() in MapOutputBuffer takes up too much cpu time
> -------------------------------------------------------------------------
>
>                 Key: HADOOP-5664
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5664
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.19.1
>            Reporter: Bryan Duxbury
>            Assignee: Chris Douglas
>            Priority: Minor
>             Fix For: 0.21.0
>
>         Attachments: 5664-0.patch, 5664-1.patch
>
>
> In examining a profile of one of my mappers today, I noticed that the method ReentrantLock.lock()
in MapTask$MapOutputBuffer seems to be taking up ~11 seconds out of around 100 seconds total.
It seems like 10% is an awfully large amount of time to spend in this lock. 

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