anchor.diff:  %% allocators in {@link allocator()}) and returns information relative to
   %% the cache hit rates. Unless memory has expected spiky behaviour, it should
   %% usually be above 0.80 (80%).
  -%% The values returned are sorted by a weight combining the lower cache hit
  -%% joined to the largest memory values allocated.
  +%%
  +%% Cache can be tweaked using three VM flags: `+MMmcs', `+MMrmcbf', and
  +%% `+MMamcbf'.
  +%%
  +%% `+MMmcs' stands for the maximum amount of cached memory segments. Its
  +%% default value is '10' and can be anything from 0 to 30. Increasing
  +%% it first and verifying if cache hits get better should be the first
  +%% step taken.
  +%%
  +%% The two other options specify what are the maximal values of a segment
  +%% to cache, in relative (in percent) and absolute terms (in kilobytes),
  +%% respectively. Increasing these may allow more segments to be cached, but
  +%% should also add overheads to memory allocation. An Erlang node that has
  +%% limited memory and increases these values may make things worse on
  +%% that point.
  +%%
  +%% The values returned by this function are sorted by a weight combining
  +%% the lower cache hit joined to the largest memory values allocated.
   -spec cache_hit_rates() -> [{{instance,instance()}, [{Key,Val}]}] when
       Key :: hit_rate | hits | alloc,
       Val :: term().
  
positive.code: %% used for. This can be related to the VM's largest multiblock carrier size
  %% (`lmbcs') and smallest multiblock carrier size (`smbcs') to specify
  %% allocation strategies regarding the block sizes to be used.
  %% @todo explain what values could lead to what strategies
  -spec average_sizes() -> [{allocator(), [{Key,Val}]}] when
      Key :: mbcs | sbcs,
      Val :: number().
  
negative.code: %% numbers, and max values, the values at the peak. Comparing both together
  %% can give an idea of whether the node is currently being at its memory peak
  %% when possibly leaky, or if it isn't. This information can in turn
  %% influence the tuning of allocators to better fit sizes of blocks and/or
  %% carriers.
  -spec fragmentation(current | max) -> [allocdata([{atom(), term()}])].
  fragmentation(Keyword) ->
      Pos = case Keyword of
  