Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Tue, 3 Nov 2015 01:26:27 +0000 (UTC)
From: "Adam B (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12706346.1396489463000.131632.1446513987834@Atlassian.JIRA>
In-Reply-To: <JIRA.12706346.1396489463000@Atlassian.JIRA>
References: <JIRA.12706346.1396489463000@Atlassian.JIRA>
 <JIRA.12706346.1396489463630@arcas>
Subject: [jira] [Commented] (MESOS-1187) precision errors with allocation
 calculations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MESOS-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14986450#comment-14986450 ] 

Adam B commented on MESOS-1187:
-------------------------------

+1 to milli-cpus and fixed point. That's what Google uses internally, and it should be good enough for Mesos too.

> precision errors with allocation calculations
> ---------------------------------------------
>
>                 Key: MESOS-1187
>                 URL: https://issues.apache.org/jira/browse/MESOS-1187
>             Project: Mesos
>          Issue Type: Bug
>          Components: allocation, master
>            Reporter: aniruddha sathaye
>            Assignee: Klaus Ma
>
> As allocations are stored/transmitted as doubles many a times precision errors creep in. 
> we have seen erroneous share calculations happen only because of floating point arithmetic. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)