This is related to the recomputation of the sampling interval whenever the environment changes and the user set a rate and not a specific interval directly.

To quote Andrei Pangin:

> If sampling period is configured as an absolute number in milliseconds, this value must be passed as is. Double conversion via Runtime.availableProcessors() / active_processor_count() is unobvious and error-prone. First, because of asymmetry: e.g. Runtime.availableProcessors() may be redefined by an agent so that its value is not aligned with active_processor_count(). Second, because number of available processors may change at runtime, e.g., by adjusting cgroup quotas.

This should be delt with.