anchor.diff:  %% 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.
  +%% 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
  
positive.code: %% 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.
  -spec cache_hit_rates() -> [{{instance,instance()}, [{Key,Val}]}] when
      Key :: hit_rate | hits | alloc,
      Val :: term().
  
negative.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.
  %%
  %% This function isn't exceptionally useful unless you know you have some
  %% specific problem, say with sbcs/mbcs ratios (see {@link sbcs_to_mbcs/0})
  %% or fragmentation for a specific allocator, and want to figure out what
  %% values to pick to increase or decrease sizes compared to the currently
  %% configured value.
  %%
  %% Do note that values for `lmbcs' and `smbcs' are going to be rounded up
  %% to the next power of two when configuring them.
  -spec average_sizes() -> [{allocator(), [{Key,Val}]}] when
      Key :: mbcs | sbcs,
      Val :: number().
  