You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Rajesh Balamohan (JIRA)" <ji...@apache.org> on 2015/09/09 04:08:45 UTC
[jira] [Updated] (TEZ-2784) optimize TaskImpl.isFinished()
[ https://issues.apache.org/jira/browse/TEZ-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajesh Balamohan updated TEZ-2784:
----------------------------------
Summary: optimize TaskImpl.isFinished() (was: micro optimization: optimize TaskImpl.isFinished())
> optimize TaskImpl.isFinished()
> ------------------------------
>
> Key: TEZ-2784
> URL: https://issues.apache.org/jira/browse/TEZ-2784
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Rajesh Balamohan
> Assignee: Rajesh Balamohan
> Attachments: AM_Profiler_snapshot.jpg, TEZ-2784.1.patch
>
>
> getInternalState() gets called multiple times within the same method within read lock. This shows up in the AM profiler when executing large jobs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)