Mini Agent: use lzma upx compression when building for release #156
Conversation
This file contains 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
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.
What does this PR do?
Compressing with
upx "$filename" --ultra-brutein a ubuntu-latest github workflow broke the executable and made it un-runnable. Using--lzmaworked correctly howeverUsing lzma compression decreases binary size by 10KB.
How to test the change?
Tested the workflow manually, verified the mini agent binary executes properly. Tested the --lzma compressed binary in Google Cloud Functions and found a negligible performance difference over 20 cold start invocations.