perf: optimize postgres on macOS/Windows for CI, remove ramdisk #21226
+186
−140
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
5ffcb9e to
b00519e
Compare
Previously we used ramdisk for embedded postgres on macOS and Windows to improve test performance. This wastes memory since data ends up cached twice: once in the ramdisk and again in postgres's own buffers. Instead, we give postgres more memory and tune it more aggressively: - Increase shared_buffers to 2GB, effective_cache_size to 4GB - Minimal WAL level, infrequent checkpoints - Disable autovacuum, JIT, logging, stats tracking - OS-specific I/O settings This gives postgres more memory to work with while simplifying CI setup.
b00519e to
4cb8daf
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously we used ramdisk for embedded postgres on macOS and Windows
to improve test performance. This wastes memory since data ends up
cached twice: once in the ramdisk and again in postgres's own buffers.
Instead, we give postgres more memory and tune it more aggressively:
This gives postgres more memory to work with while simplifying CI setup.