Use separate disks for WAL and data #984
Open
Conversation
This file contains 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
One of the performance optimization technique for insertion according to Timescaledb blog is to use separate disks for WAL & data. According to blog [1], ``` Use separate disks for WAL and data ----------------------------------- While this is a more advanced optimization that isn't always needed, if your disk becomes a bottleneck, you can further increase throughput by using a separate disk (tablespace) for the database's write-ahead log (WAL) and data. ``` [1] https://www.timescale.com/blog/13-tips-to-improve-postgresql-insert-performance/
Simplified logic of wal_fast can be found here [1] which is as follows: ``` WAL_FAST=$(dirname "$DATA_DIR")/wal_fast ``` Hence, aligning with the same logic to keep things simple. This way, it will not conflict with separate WAL directory too. [1] https://github.com/anasanjaria/spilo/blob/master/postgres-appliance/scripts/basebackup.sh
anasanjaria
force-pushed
the
add_separate_wal_directory
branch
from
90800a8
to
14fc3fc
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.
One of the performance optimization technique for insertion according to Timescaledb blog is to use separate disks for WAL & data.
According to blog [1],
[1] https://www.timescale.com/blog/13-tips-to-improve-postgresql-insert-performance/