Skip to content

backup: Use pargzip instead of pgzip for compression.#7037

Merged
deepthi merged 1 commit intovitessio:masterfrom
planetscale:enisoc-pargzip
Nov 17, 2020
Merged

backup: Use pargzip instead of pgzip for compression.#7037
deepthi merged 1 commit intovitessio:masterfrom
planetscale:enisoc-pargzip

Conversation

@enisoc
Copy link
Copy Markdown
Member

@enisoc enisoc commented Nov 14, 2020

Use pargzip instead of pgzip for compression to fix #5613. We still use pgzip for decompression because we haven't seen problems in that phase.

Signed-off-by: Anthony Yeh <enisoc@planetscale.com>
@enisoc enisoc changed the title Backups: Switch pgzip -> pargzip for lower memory usage backup: Use pargzip instead of pgzip for compression. Nov 16, 2020
@enisoc enisoc marked this pull request as ready for review November 16, 2020 23:36
Copy link
Copy Markdown
Collaborator

@deepthi deepthi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes look fine.
Do we have any before and after numbers on memory usage and time taken for backups?

@enisoc
Copy link
Copy Markdown
Member Author

enisoc commented Nov 17, 2020

In our environment, the time didn't change noticeably. With pgzip, memory usage would slowly grow throughout the backup process until OOMing. With pargzip, the memory usage is constant and insignificant compared with the memory used by mysqld.

@deepthi deepthi merged commit bb32eab into vitessio:master Nov 17, 2020
@deepthi deepthi deleted the enisoc-pargzip branch November 17, 2020 00:48
@askdba askdba added this to the v9.0 milestone Nov 27, 2020
@rvrangel rvrangel mentioned this pull request Aug 17, 2022
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

xtrabackup engine can use tons of vttablet memory

3 participants