Binary in .deb package is around twice the size of binary in .zip #1330
Labels
No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#1330
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Although they seem to be equal in functionality, the binary from the Debian package is around twice as large as the binary in the zip file. I do not know enough about building Go software to investigate why this is, but only part of the difference is accounted for by simply stripping the binary.
Resolved in
51cf8beaed
The release binaries are compressed to reduce their file size. I've changed the CI step to use the compressed binaries instead of the non-compressed ones.
Out of curiousity, what sort of runtime cost does this compression entail? Is it just a one-time thing at process creation?
It's pretty much unnoticable. We're using UPX which says it can do ~500MB/s - the binary should decompress in < 1s. As far as I know it decompresses the binary when starting it and it then runs as it would uncompressed.