Re: Precision of scalar resources

2016-02-16 Thread Alexander Rojas
+1 Strong initial first step to remove a huge headache. > On 12 Feb 2016, at 14:25, Neil Conway wrote: > > Additional precision in resource values will be discarded > (via rounding).

Re: Precision of scalar resources

2016-02-15 Thread Jörg Schad
+1 (would really help some issues we are facing with the ArangoDB framework) On Mon, Feb 15, 2016 at 8:55 AM, Benjamin Hindman wrote: > SGTM, thanks Neil! > > On Fri, Feb 12, 2016 at 2:25 PM, Neil Conway wrote: > >> tl;dr: >> >> If you use

Re: Precision of scalar resources

2016-02-15 Thread Benjamin Hindman
SGTM, thanks Neil! On Fri, Feb 12, 2016 at 2:25 PM, Neil Conway wrote: > tl;dr: > > If you use resource values with more than three decimal digits of > precision (e.g., you are launching a task that uses 2.5001 CPUs), > please speak up! > > > > Mesos uses floating

Re: Precision of scalar resources

2016-02-14 Thread Joris Van Remoortere
+1 Thanks for taking this on Neil! — *Joris Van Remoortere* Mesosphere On Fri, Feb 12, 2016 at 11:25 PM, Neil Conway wrote: > tl;dr: > > If you use resource values with more than three decimal digits of > precision (e.g., you are launching a task that uses 2.5001 CPUs),

Precision of scalar resources

2016-02-12 Thread Neil Conway
tl;dr: If you use resource values with more than three decimal digits of precision (e.g., you are launching a task that uses 2.5001 CPUs), please speak up! Mesos uses floating point to represent scalar resource values, such as the number of CPUs in a resource offer or dynamic reservation.