Skip to content
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.

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

2.16 faster flake lock parsing #10183

Conversation

johnrichardrinehart
Copy link

Motivation

This is the same as #10055 #10170 #10057 #10169 but for 2.16-maintenance.

I'd also ask for this to be backported to

  1. 2.15-maintenance
  2. 2.14-maintenance
  3. 2.13-maintenance
  4. 2.12-maintenance
  5. 2.11-maintenance
  6. 2.10-maintenance
  7. 2.9-maintenance
  8. 2.8-maintenance
  9. 2.7-maintenance
  10. 2.6-maintenance
  11. 2.5-maintenance
  12. 2.4-maintenance

Context

Priorities and Process

Add 👍 to pull requests you find important.

The Nix maintainer team uses a GitHub project board to schedule and track reviews.

This PR reduces the creation of short-lived basic_json objects while
parsing flake.lock files. For large flake.lock files (~1.5MB) I was
observing ~60s being spent for trivial nix build operations while
after this change it is now taking ~1.6s.

(cherry picked from commit 7fd0de3)
@johnrichardrinehart
Copy link
Author

@roberth @edolstra Please take note of this backport request. Like in the previous PRs I'm kindly requesting the be backported to all prior known-compatible (no merge conflict no compilation failures) branches.

@roberth roberth merged commit e8334d1 into NixOS:2.16-maintenance Mar 7, 2024
8 checks passed
@roberth
Copy link
Member

roberth commented Mar 7, 2024

We normally don't backport beyond the default Nix of NixOS stable (ie NixOS 23.11, Nix 2.18). Do you really need this?

@johnrichardrinehart
Copy link
Author

johnrichardrinehart commented Mar 7, 2024

Thanks for your attention @roberth . Unfortunately, I work with a large number of users, some of whom are unable to update past nix 2.8 (not 2.18). So, anything before that is a nice-to-have.

But, it would make sense (considering the scope/risk of the change weighed against the performance benefit) to backport this all the way to nix 2.4 to benefit all potential users.

Alternatively (but not ideally), a .patch could be introduced into nixos/nixpkgs but that would only benefit consumers of nixos/nixpkgs not all users of nix who are keeping their sources up-to-date.

Copy link

github-actions bot commented Mar 7, 2024

Successfully created backport PR for 2.4-maintenance:

Copy link

github-actions bot commented Mar 7, 2024

Git push to origin failed for 2.4-maintenance with exitcode 1

Copy link

github-actions bot commented Mar 7, 2024

Successfully created backport PR for 2.15-maintenance:

Copy link

github-actions bot commented Mar 7, 2024

Git push to origin failed for 2.4-maintenance with exitcode 1

Copy link

github-actions bot commented Mar 7, 2024

Successfully created backport PR for 2.14-maintenance:

Copy link

github-actions bot commented Mar 7, 2024

Git push to origin failed for 2.15-maintenance with exitcode 1

Copy link

github-actions bot commented Mar 7, 2024

Git push to origin failed for 2.4-maintenance with exitcode 1

Copy link

github-actions bot commented Mar 7, 2024

Successfully created backport PR for 2.13-maintenance:

Copy link

github-actions bot commented Mar 7, 2024

Git push to origin failed for 2.14-maintenance with exitcode 1

Copy link

github-actions bot commented Mar 7, 2024

Git push to origin failed for 2.15-maintenance with exitcode 1

Copy link

github-actions bot commented Mar 7, 2024

Git push to origin failed for 2.4-maintenance with exitcode 1

Copy link

github-actions bot commented Mar 7, 2024

Successfully created backport PR for 2.12-maintenance:

Copy link

github-actions bot commented Mar 7, 2024

Git push to origin failed for 2.13-maintenance with exitcode 1

Copy link

github-actions bot commented Mar 7, 2024

Git push to origin failed for 2.14-maintenance with exitcode 1

Copy link

github-actions bot commented Mar 7, 2024

Git push to origin failed for 2.15-maintenance with exitcode 1

Copy link

github-actions bot commented Mar 7, 2024

Git push to origin failed for 2.4-maintenance with exitcode 1

Copy link

github-actions bot commented Mar 7, 2024

Successfully created backport PR for 2.11-maintenance:

Copy link

github-actions bot commented Mar 7, 2024

Git push to origin failed for 2.12-maintenance with exitcode 1

Copy link

github-actions bot commented Mar 7, 2024

Git push to origin failed for 2.13-maintenance with exitcode 1

Copy link

github-actions bot commented Mar 7, 2024

Git push to origin failed for 2.14-maintenance with exitcode 1

Copy link

github-actions bot commented Mar 7, 2024

Git push to origin failed for 2.15-maintenance with exitcode 1

Copy link

github-actions bot commented Mar 7, 2024

Successfully created backport PR for 2.10-maintenance:

Copy link

github-actions bot commented Mar 7, 2024

Successfully created backport PR for 2.9-maintenance:

Copy link

github-actions bot commented Mar 7, 2024

Successfully created backport PR for 2.8-maintenance:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants