Skip to content

docs: include specific benchmark numbers in build optimization note #2110

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.

Sign up for GitHub

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

Merged
devantler merged 2 commits into from
Feb 9, 2026
Merged

docs: include specific benchmark numbers in build optimization note #2110

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b754222
Initial plan
Copilot Feb 9, 2026
9522c20
docs: add specific benchmark numbers and link to #2095
Copilot Feb 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ go build ./...
go build -ldflags="-s -w" -o ksail-optimized
```

> **Note:** Release builds use `-ldflags="-s -w"` to strip debug symbols, which typically reduces binary size by around 25–30% (exact size varies by OS/arch, Go version, and dependencies). Development builds include debug symbols for a better debugging experience.
> **Note:** Release builds use `-ldflags="-s -w"` to strip debug symbols, which can significantly reduce binary size (in some cases by ~25–35%; see [#2095](https://github.com/devantler-tech/ksail/pull/2095) for an example benchmark where Darwin/AMD64 binaries went from 302MB → 217MB, ~28%). Actual size varies by OS/arch, Go version, and dependencies. Development builds include debug symbols for a better debugging experience.

### Test

Expand Down