fix: move logs up #15

Merged

jalil merged 1 commit from push-yrtyyytpwmuk into main 2025-03-10 23:50:51 +01:00

Conversation 1 Commits 1 Files changed 1 +4 -2

jalil commented 2025-03-10 23:49:44 +01:00

Owner

Copy link

Otherwise they are missing from the failure case

Otherwise they are missing from the failure case

jalil self-assigned this 2025-03-10 23:49:44 +01:00

jalil added 1 commit 2025-03-10 23:49:44 +01:00

fix: move logs up ... 5c40a31e3e

Otherwise they are missing from the failure case

forgejo-actions commented 2025-03-10 23:49:51 +01:00

Copy link

Flake output sizes

Definitions

• Name: the name of the package/configuration.
• Size: the closure size (size on disk/NAR size + all transitive dependencies).
• NAR Size: the size of the build output (package without the dependencies).
• [NAR] Size Change: the amount changed compared to the main branch.

Tips on reading this data

• For NixOS configurations you generally care only about the Size (closure size/size on disk).
  • Reduce the Size by disabling unneeded services/default packages.
• For Packages you care about both the Size and the NAR Size.
  • Reduce the NAR Size by reducing the size of the build outputs, e.g. don't copy unnecessary data to the $out dir, optimize binaries for size, etc.
  • Reduce the Size by reducing the dependencies (e.g. buildInputs).
  • Don't worry too much about size, some dependencies are deduplicated, e.g. glibc adds ~40MiB to the Size, but is generally shared by ~every binary on the system, so, chances are, you are already including it from somewhere else and statically linking with e.g. musl is not gonna improve things.

Packages

Name	Size	Size Change	NAR Size	NAR Size Change
hello	32MiB	0B	230KiB	0B

<!-- AUTOGENERATED by nix-flake-outputs-size action --> ## Flake output sizes <details><summary><b>Definitions</b></summary> - `Name`: the name of the package/configuration. - `Size`: the closure size (size on disk/NAR size + all transitive dependencies). - `NAR Size`: the size of the build output (package without the dependencies). - `[NAR] Size Change`: the amount changed compared to the main branch. </details> <details><summary><b>Tips on reading this data</b></summary> - For NixOS configurations you generally care only about the `Size` (closure size/size on disk). - Reduce the `Size` by disabling unneeded services/default packages. - For Packages you care about both the `Size` and the `NAR Size`. - Reduce the `NAR Size` by reducing the size of the build outputs, e.g. don't copy unnecessary data to the $out dir, optimize binaries for size, etc. - Reduce the `Size` by reducing the dependencies (e.g. `buildInputs`). - Don't worry too much about size, some dependencies are deduplicated, e.g. `glibc` adds ~40MiB to the `Size`, but is generally shared by ~every binary on the system, so, chances are, you are already including it from somewhere else and statically linking with e.g. `musl` is not gonna improve things. </details> ## Packages | Name | Size | Size Change | NAR Size | NAR Size Change | |------|-----:|------------:|---------:|----------------:| | `hello` | 32MiB | 0B | 230KiB | 0B |

jalil merged commit 5c40a31e3e into main 2025-03-10 23:50:51 +01:00

jalil deleted branch push-yrtyyytpwmuk 2025-03-10 23:50:51 +01:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

jalil

2 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: jalil/nix-flake-outputs-size#15

No description provided.