jalil/nix-flake-outputs-size
1
0
Fork 0
Code Issues Pull requests Activity Actions

feat: add nix for formatting #13

Merged
jalil merged 1 commit from push-rzqqtmozzmmq into main 2025-03-10 23:23:42 +01:00
Conversation 1 Commits 1 Files changed 9 +314 -121
jalil commented 2025-03-10 23:18:23 +01:00
Owner

Also adds CI tests!

Also adds CI tests!
jalil self-assigned this 2025-03-10 23:18:23 +01:00
jalil added 1 commit 2025-03-10 23:18:23 +01:00 
Also adds CI tests!
jalil force-pushed push-rzqqtmozzmmq from 0f0f05bb5e to 01fae63422 2025-03-10 23:20:38 +01:00 Compare
jalil force-pushed push-rzqqtmozzmmq from 01fae63422 to 73142cfab8 2025-03-10 23:22:19 +01:00 Compare
forgejo-actions commented 2025-03-10 23:22:31 +01:00
First-time contributor

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 32MiB 230KiB 230KiB
<!-- AUTOGENERATED by nix-flake-outputs-size action --> # 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 | 32MiB | 230KiB | 230KiB |
jalil merged commit 73142cfab8 into main 2025-03-10 23:23:42 +01:00
jalil deleted branch push-rzqqtmozzmmq 2025-03-10 23:23:42 +01:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
jalil
2 participants
Notifications
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#13
No description provided.
Delete branch "push-rzqqtmozzmmq"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?