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: %%
  %% When a specific piece of data is allocated, it is compared to a threshold,
  %% called the 'single block carrier threshold' (`sbct'). When the data is
  %% larget than the `sbct', it gets sent to a single block carrier. When the
  %% data is smaller than the `sbct', it gets placed into a multiblock carrier.
  %%
  %% Ideally, most of the data should fit inside main multiblock carriers. If
  %% most of the data ends up in `sbcs', you may need to adjust the multiblock
  %% carrier sizes, specifically the maximal value (`lmbcs').
  %%
  %% Given the value returned is a ratio of sbcs/mbcs, the higher the value,
  %% the worst the condition. The list is sorted accordingly.
  
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().
  