Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update README to document --pool-size parameter to wal_push #67

Closed
wants to merge 1 commit into from
Closed

Update README to document --pool-size parameter to wal_push #67

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions README.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -499,6 +499,21 @@ Quieter Logging
To restrict log statements to warnings and errors, use the ``--terse``
option. This is supported on all WAL-E operations.

Increasing throughput of wal_push
'''''''''''''''''''''''''''''''''

In certain situations, the wal_push process can take long enough that it
can't keep up with WAL segments being produced by the DB, which can lead
to unbounded disk usage.

You can instruct wal-e to pool WAL segments together and send them in groups
by passing the "--pool-size / -p" parameter to wal_push. This has been
experienced to significantly increase wal_push throughput.

In versions <=0.6.x, --pool-size defaults to 1.

As of version 0.7.x, --pool-size defaults to 8.


Development
-----------
Expand Down