Skip to content
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

[CI] Build/Test Improvement suggestions from EIO #561

Open
3 tasks
mallardduck opened this issue Aug 13, 2024 · 0 comments
Open
3 tasks

[CI] Build/Test Improvement suggestions from EIO #561

mallardduck opened this issue Aug 13, 2024 · 0 comments

Comments

@mallardduck
Copy link
Member

  • - It looks like you could probably do a go mod download prior to tests/builds, if you wanted to cache that.
  • - 76sec to build the binary, might be throwing a few more CPU cores at it to see how much it cuts down?
  • - Not performance related, but you may want to consider adding -s to your GOLDFLAGS (which doesn’t break stack traces, unlike post-processing it with strip can do), and possible -w (unless the app uses or exposes an interface for pprof profiling info). Both of those can cut down your binary size, and smaller containers are better for everyone.

NOTE: just for long term tracking and memory here. Not a call to action.

@mallardduck mallardduck added this to the CI milestone Aug 13, 2024
@MKlimuszka MKlimuszka removed this from the CI milestone Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants