+1.
As an alternative... an execute-on-read directive of ProxyBalancerPrecision
or similarly named directive (default 100, but drop or add decimals as
they will)
would let anyone add in or sub out a decimal.
My thought, taking away 1000 (3 decimal) from 2bn really wouldn't be a
hardship on any
Sounds good to me :)
> On Aug 4, 2017, at 9:02 PM, Jim Riggs wrote:
>
>> On 3 Aug 2017, at 08:30, Jim Jagielski wrote:
>>
>> It's just GUI magic... Basically, it will internally take '1.1' and
>> convert it to 11, 1.0 to 10, etc...
>
> If that's the
> On 3 Aug 2017, at 08:30, Jim Jagielski wrote:
>
> It's just GUI magic... Basically, it will internally take '1.1' and
> convert it to 11, 1.0 to 10, etc...
If that's the case, I would recommend going 2 decimal places (1.1 = 100, 1.25 =
125, etc.) to allow using percentages.
It's just GUI magic... Basically, it will internally take '1.1' and
convert it to 11, 1.0 to 10, etc...
No struct or field changes.
> On Aug 2, 2017, at 3:39 PM, Jim Riggs wrote:
>
>> On 2 Aug 2017, at 12:33, Jim Jagielski wrote:
>>
>> I'll be adding
On Wed, Aug 2, 2017 at 12:33 PM, Jim Jagielski wrote:
> I'll be adding some code to allow for lbfactors to be
> single decimal numbers (like 1.1, 2.5, etc...)... People
> have asked "How do I change it so that machine B is like 10%
> preferred" and I mention that "Well, you
> On 2 Aug 2017, at 12:33, Jim Jagielski wrote:
>
> I'll be adding some code to allow for lbfactors to be
> single decimal numbers (like 1.1, 2.5, etc...)... People
> have asked "How do I change it so that machine B is like 10%
> preferred" and I mention that "Well, you could