jemalloc/test
Dmitry Ilvokhin 3820e38dc1 Remove validation for HPA ratios
Config validation was introduced at 3aae792b with main intention to fix
infinite purging loop, but it didn't actually fix the underlying
problem, just masked it. Later 47d69b4ea was merged to address the same
problem.

Options `hpa_dirty_mult` and `hpa_hugification_threshold` have different
application dimensions: `hpa_dirty_mult` applied to active memory on the
shard, but `hpa_hugification_threshold` is a threshold for single
pageslab (hugepage). It doesn't make much sense to sum them up together.

While it is true that too high value of `hpa_dirty_mult` and too low
value of `hpa_hugification_threshold` can lead to pathological
behaviour, it is true for other options as well. Poor configurations
might lead to suboptimal and sometimes completely unacceptable
behaviour and that's OK, that is exactly the reason why they are called
poor.

There are other mechanism exist to prevent extreme behaviour, when we
hugified and then immediately purged page, see
`hpa_hugify_blocked_by_ndirty` function, which exist to prevent exactly
this case.

Lastly, `hpa_dirty_mult + hpa_hugification_threshold >= 1` constraint is
too tight and prevents a lot of valid configurations.
2024-11-20 18:59:07 -08:00
..
analyze Tcache batching: Plumbing 2024-05-22 10:30:31 -07:00
include/test Add batching to arena bins. 2024-05-22 10:30:31 -07:00
integration Make headers self-contained by fixing `#include`s 2023-07-14 09:06:32 -07:00
src Enable a few additional warnings for CI and fix the issues they uncovered 2023-08-11 13:56:23 -07:00
stress increase the ncached_max in fill_flush test case to 1024 2024-08-06 13:16:09 -07:00
unit Remove validation for HPA ratios 2024-11-20 18:59:07 -08:00
test.sh.in Print test error messages in color when stderr is a terminal 2023-07-13 13:03:23 -07:00