Nixpkgs evaluation time share #2
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
qyriad/rfd-modular-dynamicism#2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
The performance benchmarks compare relatively lean NixOS system closures (a singular service, plus dependencies) asd show relatively small time difference compared to the difference implied on a larger closures. It would maybe be nice to see the static overhead of evaluating nixpkgs mentioned, since, from what I know (and, of course, this may be wrong) that would be a large part of evaluating e.g. grafana's systemd unit file, and would likely be a similar share of performance on bath the partial and full closure evaluations, at least in the examples in the document.