-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
Strip release binaries #14126
Comments
@szepeviktor Can you help share your use case and why you're hoping to see this change? |
@amyblais Of course. Not stripped binaries are BIG, taking up memory in vain, |
"stripping" is a technical term, not equal to the English word. So not stripped binaries go to developers and testers, |
@szepeviktor - Thanks for filing the issue. Reducing size is indeed important, but so is the ability to debug crashes in production. The tipping point would usually be when the difference in binary size is so big, that is dwarfs the need to be able to debug in production. I just did some testing and the binary size just went down from 57MB to 43MB. Granted it's still 14MB, but I am curious to know how much of an impact is it making in your environment ? Is it something that you consider good to have ? Or you are actually facing performance issues with binary size ? That being said, the Go runtime is becoming smarter every release and it has started to compress the debug symbols. And we have also started to make small changes like using the There are these specific issues from the Go team golang/go#6853, golang/go#26379 which concerns reducing binary size if you are interested. |
I see. QA is in my focus. So using QA tools in development could make debugging unnecessary! Some highly popular binaries are 130 KB is size.
14 MB is 100× |
I give you my basic trio of zero-coverage tests I enforce at every client.
Go is Chinese to me, so these may be built-in or even impossible! |
Releases on releases.mattermost.com contain not stripped binaries.
Please consider going from 50MB -> 38MB in case of
mattermost
Thank you.
The text was updated successfully, but these errors were encountered: