Thanks Bibin A Chundatt for the patch.
The said issue due to conversion does exist.
So it does make sense to have a float version of the method in ResourceCalculator to avoid such issues due to conversion.
We can alternatively strip off the extraneous decimal digits too but that would not be as straightforward.
And in this case, as ResourceCalculator is annotated as Private, we can add an abstract method to it as well.
However, it seems the values passed to ResourceCalculator#multiplyAndNormalizeUp are all in float. But as double has larger range and more precision, it might be better, in general as a data type, when we do calculations in scheduler.
So can't we alternatively read these configurations as double too? Thoughts?