The ``max_threads``, ``max_block_size``, ``max_download_threads`` and parallel parsing and formatting settings were declared in a ``<profile>`` block of ``config.d/low-resources.xml``. ClickHouse only reads profile settings from users configuration files, so they were silently ignored and the server used its defaults (one thread per core, larger blocks). Following the Plausible Community Edition change of ``v3.2.0`` (its pull request 265), ``config.d/low-resources.xml`` now keeps only the server setting ``mark_cache_size``, and the profile settings move to ``users.d/default-profile-low-resources-overrides.xml``, inside ``<profiles>``. ``system.settings`` now reports ``max_threads`` 1. Assisted-by: Claude:claude-opus-5-5
757 B
757 B
Info
This charm is provided to work with plausible charm
Configuration files come from
https://github.com/plausible/community-edition/ (clickhouse/).
Usage
Added automatically by the plausible charm (event-db relation).
Low memory settings
config.d/low-resources.xml: server settings (mark_cache_size).users.d/default-profile-low-resources-overrides.xml: settings of thedefaultprofile (max_threads1, …). ClickHouse reads profiles only from users configuration files: inconfig.dthey were ignored.
Check that they apply:
docker exec <container> clickhouse-client -q \
"SELECT name, value FROM system.settings WHERE name = 'max_threads'"