Skip to content

Conversation

@pablomh
Copy link
Contributor

@pablomh pablomh commented Dec 9, 2025

This PR is opened for people to comment on it :)

Something similar to this is how I envision we should autoconfigure (at least) PostgrSQL tuning.

All the numbers derive only from one variable: foreman_puma_threads_max, which (right now) would be the only one to "play" with.

This approach tries to come up with similar figures to what current --tuning would return for the same hardware.

@pablomh pablomh force-pushed the tuning_postgresql_dynamic branch from 9c3b2e0 to 681c4e9 Compare December 9, 2025 16:08
postgresql_max_connections: 500
postgresql_shared_buffers: 512MB
postgresql_effective_cache_size: 1GB
postgresql_pulp_connections_count: "{{ pulp_worker_count + pulp_content_service_worker_count + pulp_api_service_worker_count }}"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On the design, as we aim for role isolation, this should not reference the other roles variables. The right place would be something like vars/defaults.yml like you have in the PR.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PTAL at the new version.

@pablomh pablomh force-pushed the tuning_postgresql_dynamic branch 6 times, most recently from 090aaed to 5f7b04d Compare December 11, 2025 23:58
@pablomh pablomh mentioned this pull request Dec 19, 2025
@pablomh pablomh force-pushed the tuning_postgresql_dynamic branch from 5f7b04d to 489a5da Compare December 22, 2025 16:44
@pablomh pablomh force-pushed the tuning_postgresql_dynamic branch from 489a5da to 024a7ea Compare December 22, 2025 16:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants