-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
explain cache misses #10695
Comments
Triaged in Nix team meeting:
|
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/2024-05-15-nix-team-meeting-minutes-146/45491/1 |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/overlaying-packages-using-cuda-to-use-zluda/45374/5 |
i thought about this a bit more. @fricklerhandwerk i think caches currently not having the info needed for this means we could address this for the future by allowing caches to start storing not only a hash's build results, but also the (instantiated) derivation that produced that result, as we do in i think the concern around combinatorial explosion could be alleviated by:
i hope that i properly understood the raised concern, and that this might go some way toward addressing it. |
@KiaraGrouwstra what you write indicates to me that the mechanism you desire may indeed be more suitable to be implemented on top of Nix rather than as part of it, for example as part of a (still hypothetical) Nixpkgs CLI. I have a hard time imagining how caching derivations would help, because all that gives you are more opaque store paths. What we'd really need for actionable suggestions is information about Nixpkgs recipe parameters, and we simply don't have them at the Nix layer. The derivation's Another thing that could get us closer to your vision may be a generic cache mechanism where one adds an attribute set to the argument to |
@fricklerhandwerk thanks for your response. i agree a generic caching mechanism could help facilitate this, given a nix cli (i think this isn't specific to nixpkgs) and cache implementing it. |
Is your feature request related to a problem? Please describe.
nix either builds derivations, or manages to reuse existing build results from a cache.
as a user, being able to use cached builds is generally nice.
unfortunately, when no build is found in the cache, the user is generally left without much knowledge as to why.
Describe the solution you'd like
in case of cache misses on a package, provide the user with feedback on alternative configurations for a package that might have resulted in a cache hit: maybe package foo with this version x of dependency bar is not in the cache, but using version y it might have been.
Describe alternatives you've considered
The text was updated successfully, but these errors were encountered: