LPD-68592 Import/export via creating and extracting tar files after image creation to avoid large Docker contexts #139
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
holatuwol
changed the title
holatuwol
force-pushed
the
lec-LPD-68592
branch
from
4d6726c to
417bf97
Compare
…mage creation to avoid large Docker contexts
…ves and to avoid any limitations in Java's zip implementation
holatuwol
force-pushed
the
lec-LPD-68592
branch
from
417bf97 to
2db6a8c
Compare
|
Sharing a workspace was similarly slow, so I also updated the pull request to use 7z, which gives us a progress bar and support for files greater than 4GB, and LZMA2, which will use more CPU threads to speed up compression. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Recently I ran into a performance issue loading a 100 GB exported_data folder. I waited for a little over an hour and it still hadn't finished, which seemed strange to me because loading 100 GB shouldn't take long at all given that we're just copying files.
Manually running the
docker compose upcommand, I found that copying files to the Docker context was really slow, and so I rewrote the export and import to leverage .tar files, and the import process completed in about 5 minutes since it avoided the slow step of dealing with the large Docker context.