Mailing-List: contact dev-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Fri, 8 Nov 2013 19:50:17 +0000 (UTC)
From: "Jie Yu (JIRA)" <jira@apache.org>
To: dev@mesos.apache.org
Message-ID: <JIRA.12663914.1376598874408.43862.1383940217455@arcas>
In-Reply-To: <JIRA.12663914.1376598874408@arcas>
References: <JIRA.12663914.1376598874408@arcas>
Subject: [jira] [Updated] (MESOS-645) Improve the performance of Future.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jie Yu updated MESOS-645:
-------------------------

    Attachment:     (was: Screen Shot 2013-08-27 at 9.51.21 AM.png)

> Improve the performance of Future.
> ----------------------------------
>
>                 Key: MESOS-645
>                 URL: https://issues.apache.org/jira/browse/MESOS-645
>             Project: Mesos
>          Issue Type: Sub-task
>            Reporter: Jie Yu
>            Assignee: Jie Yu
>            Priority: Minor
>
> Future is performance critical. The current implementation of Future uses a Latch which leverages a process which is not efficient (e.g. user level switches, process creation/termination cost, etc.).
> Our idea is to create the Latch in each Future lazily so that in common cases, we don't need to create a Latch.


--
This message was sent by Atlassian JIRA
(v6.1#6144)