Optimize PostgreSQL parameters for SSD storage #536
Merged
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.
Purpose
This PR introduces several adjustments to the PostgreSQL configuration to optimize performance for environments using SSD storage.
Key Changes
random_page_cost
is set to1.1
, down from the default suited for HDDs, to leverage the faster random read capabilities of SSDs.effective_io_concurrency
is increased to200
to take advantage of SSD's higher parallel I/O capabilities. This is a significant change from the default setting, which is optimized for traditional HDDs.These changes are aimed at harnessing the full potential of SSDs, ensuring better performance of the database system, especially in high I/O demand environments.