fossilize-prune: add --max-size option#293
Open
daniel-schuermann wants to merge 1 commit intoValveSoftware:masterfrom
Open
fossilize-prune: add --max-size option#293daniel-schuermann wants to merge 1 commit intoValveSoftware:masterfrom
daniel-schuermann wants to merge 1 commit intoValveSoftware:masterfrom
Conversation
This option allows to prune pipelines to a specified size. It does not account for application info links. The pipelines are roughly split as - 50% Raytracing pipelines - 30% Compute pipelines - 20% Graphics pipelines
daniel-schuermann
force-pushed
the
pipeline-whitelist
branch
from
668218b to
346c897
Compare
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
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.
Adds a convenient way to trim a fossilize archive to a desired size. The selection which pipelines end up in the output-db is pretty much random, so the use case is quite limited. It doesn't consider the additional size of application info links nor the database header of 16 bytes. But if you use --skip-application-info-links, then the archive will end up at most 16 bytes larger than the provided size (probably smaller, because it doesn't emit partial pipelines).
The pipelines are roughly split as