-
Notifications
You must be signed in to change notification settings - Fork 81
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.
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
Use btrfs with compress to further reduce storage consumption #23
Comments
Sounds interesting. Do you have any ballpark figures, how good the compression works and how compression affects CPU usage? |
In my old action I used |
That could be an interesting option for those requiring even more space. Would you mind creating a merge request with btrfs as an option? |
I would very greatly appreciate this, and can confirm BTRFS compression plays nice with GitHub Actions and 'maximize-build-space'. Since I am already running a compressed BTRFS ChRoot on a loopback image within GitHub Actions after the 'maximize-build-space' step. Yes, the kernels used by GitHub Actions have full support and all. This would improve my margins from only a few gigabytes, to a several more gigabytes. Compression is a good upwards of 30%-50%, and much, much more importantly, compression eliminates unused disk space from loopback filesystems in which a 'dd if=/dev/zero of=./fill' has been applied recently. EDIT: You might find relevant code scattered around relevant shell code projects I do some work on... |
Looks like this line could change to use btrfs instead of ext4 : https://github.com/easimon/maximize-build-space/blob/master/action.yml#L176 And this line could enable compression : https://github.com/easimon/maximize-build-space/blob/master/action.yml#L181 |
I've made some progress on my fork libenc/maximize-build-space@add-btrfs-support. These changes have actually been running for a while in my private projects brefore this fork and have shown to be stable enough, so I decided to share them out. Since there is already a PR #37 about this issue, I'll wait for some feedback, and add some docs related if needed. As turning on the compression with BTRFS may have a large performance impact and also for compatibility reasons, an option has been added to explicitly turn on the BTRFS ( |
Before I knew this action I was using btrfs with compress to workaround my own space issue. I see this action is still using ext4, so this could be another way to accommodate large projects.
The text was updated successfully, but these errors were encountered: