package irmin-bench
Install
dune-project
Dependency
Authors
Maintainers
Sources
sha256=11fc2570bdbfd48478c89113fc801084a84a9a2c12d9bf8c64e05ce64ae19bd7
sha512=2171699ca24dec5c9c908a2676b272e034c14eb17f7052a794535e52af0be40be68a689e59c0a640ee244b11703320483f4d0c261542e6242ba23a8f1272b9b0
doc/irmin-bench.traces/Irmin_traces/Trace_stat_summary_utils/index.html
Module Irmin_traces.Trace_stat_summary_utilsSource
Utilities to summarise data.
This file is NOT meant to be used from Tezos, as opposed to some other "trace_*" files.
snap_to_integer ~significant_digits v is Float.round v if v is close to Float.round v, otherwise the result is v. significant_digits defines how close things are.
Examples:
When significant_digits is 4 and v is 42.00001, snap_to_integer v is 42..
When significant_digits is 4 and v is 42.001, snap_to_integer v is v.
val create_pp_real :
?significant_digits:int ->
float list ->
Format.formatter ->
float ->
unitcreate_pp_real examples is pp_real, a float pretty-printer that adapts to the examples shown to it.
It is highly recommended, but not mandatory, for all the numbers passed to pp_real to be included in examples.
When all the examples are integers, the display may be different. The examples that aren't integer, but that are very close to be a integers are counted as integers. significant_digits is used internally to snap the examples to integers.
create_pp_seconds examples is pp_seconds, a time span pretty-printer that adapts to the examples shown to it.
It is highly recommended, but not mandatory, for all the numbers passed to pp_seconds to be included in examples.
Pretty prints a percent in a way that always takes 4 chars.
Examples: 0. is " 0%", 0.00001 is "0.0%", 0.003 is "0.3%", 0.15 is " 15%", 9.0 is 900%, 700. is 700x, 410_000.0 is "4e6x" and 1e100 is "++++".
Negative inputs are undefined.
Functional Exponential Moving Average (EMA).
Functional summary for a variable that has zero or more occurences per period. accumulate is expected to be called in_period_count times before finalise is.
See Trace_stat_summary for an explanation and an example.