feat: add kong config with nginx_worker_processes option #1271
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
This PR adds the ability to configure Kong's
nginx_worker_processes
value via the below TOML config:What is the current behavior?
When running in memory-constrained environments, Kong/Nginx may spawn an excessive number of workers, drastically increasing memory usage.
What is the new behavior?
This PR allows users to fine-tune the number of Kong/Nginx worker processes when desired. If no configuration is provided, the previous behavior (
auto
) is used.Additional context
For my use case, this allowed me to cut memory usage of the entire Supabase Docker compose by 79%! (1487 MiB -> 312 MiB) by setting it to just
1
(I'm not especially concerned about the reduced routing performance).