Stijn Debrouwere
Stijn Debrouwere
Quantize to somewhere in between a magnitude. For example: * `ceil(55.25, 1.2) => 55.26` * `floor(55.25, 1.2) => 55.24` * `round(55.3333, 2.5) => 55.335` * `round(12.345, 1.1) == round(12.345, 2)...
When rounding, optionally ensure that `sum(round(values)) == round(sum(values))` by rounding some numbers in the opposite direction than the one dictated by convention. The rounding error should be minimized, e.g. prefer...
Separating out two or three examples into separate tables would make it clearer how business notation respects same-place-means-same-magnitude and would just generally be clearer.
Currently, this isn't massaged quite as well as the OverTime reports are, sometimes even crashing.
It might be interesting to have the option to log extensively (when setting up a cluster and seeing how it behaves for the first couple of days) or less extensively...
It gets to be really verbose to have to put `docker pull` and `etcsnapshot` in every service definition. Instead, we could put it in a separate service and have other...
When doing e.g. `page.insights.lifetime('page_fans').get()`, the Graph API doesn't return a single lifetime metric but instead a range of older values. So it looks like behind the scenes, this metric isn't...