build(ci): optimize Cargo release for program

[Rudxain]

https://doc.rust-lang.org/cargo/reference/profiles.html

[deepsource-io]

Here's the code health analysis summary for commits 4b12d03..1b3e1f3. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Rust	✅ Success		View Check ↗
Test coverage	⚠️ Artifact not reported	Timed out: Artifact was never reported	View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[AnonymousWP]

Because the Cargo.toml is used when building the assets, right? And assets are being build when a tag is pushed for a new version.🙂 Let me know if that way of thinking is incorrect.

[adhirajsinghchauhan]

This is sure to lead to much slower code. IMO remove this line, it doesn't really help much with executable sizes, so let it be at the default of 16.

[Rudxain]

I could only find this rust-lang/rust#47745 , but I'm not sure how to interpret all the linked issues 😕

Should we set it to 4 instead?

[adhirajsinghchauhan]

I believe that's specific to lto="thin", which we don't use. We don't have any benchmarks for code performance, so the only test we can do is build with and without defaults codegen values, and compare file sizes.

[adhirajsinghchauhan]

I'm interested to see the size differences between panic unwind and abort. Could you post comparisons by building the latest release with both options?

[Rudxain]

cargo build --release; stat -c%s target/release/uad-ng on 3 branches:

• main 16261816
• build/opt-release 14346792
• default-codegen-units (local) 14748040

env:

• cargo 1.81.0 (2dbb1af80 2024-08-20)
• apt-cache show clang | grep Version: | cut -d' ' -f2 1:16.0-58.1
• apt-cache show mold | grep Version: | cut -d' ' -f2 2.33.0+dfsg-1
• 4 logical CPU cores