| 15 Dec 2025 |
hexa (UTC+1) | looks up from here | 02:47:37 |
hexa (UTC+1) | might be a transient path issue | 02:47:46 |
pdealbera | Did you reproduced the same issue? | 02:49:57 |
hexa (UTC+1) | ❯ curl https://cache.nixos-cuda.org/mhf691zwwjrqi8b6an14pblyqbzwn1v2.narinfo
missed hash⏎
| 02:55:27 |
pdealbera | Thanks! Not the same thing, I can't reach the host:
❯ curl https://cache.nixos-cuda.org/mhf691zwwjrqi8b6an14pblyqbzwn1v2.narinfo
curl: (7) Failed to connect to cache.nixos-cuda.org port 443 after 675 ms: Could not connect to server
| 02:59:52 |
pdealbera | But that means its probably a thing on my end. | 03:00:06 |
hexa (UTC+1) | the server is hosted in helsinki at hetzner fwiw | 03:01:23 |
connor (burnt/out) (UTC-8) | Slightly off topic but for those of you who use Hydra or nix-eval-jobs with lots of eval time fetchers or substitution, you may be interested in some WIP I’ve been doing to improve that use case https://gist.github.com/ConnorBaker/9e31d3b08ff6d4ac841928412131fe15 | 09:42:32 |
connor (burnt/out) (UTC-8) |  Download Numbers from doing a shallow eval (not forcing recursion) of Haskell.nix’s hydraJobs which has a number of flake inputs (and I think also does IFD?) | 09:46:39 |
connor (burnt/out) (UTC-8) |  Download I’m also trying to look into using Intel VTune to get a better idea of Nix bottlenecks/areas for improvement
VTune is currently packaged in Nixpkgs through the Intel-oneapi stuff but I couldn’t get it working without using the latest version. I’ll probably try upstreaming the changes at some point unless someone beats me to it. | 09:48:44 |
yorik.sar | Did you by any chance run a comparison for more common use-case of evaluating a sizeable NixOS config, for example? Just to see what those locks do to less parallel workload. | 10:53:30 |
yorik.sar | I’m surprised to see parser there - how much code were you evaluating? | 10:54:09 |
yorik.sar | I think I already saw some lock implementation in Nix code, probably better to reuse that one. Also, Nix code seems to prefer RAII (smth like { auto _thelock = lock.get(); … }) rather than passing continuation to a function (withLock(…)). | 10:56:46 |
yorik.sar |
I'd like to do further work to deduplicate queries for .narinfo and the like, since Nix already generates quite the network storm by firing them off in serial.
I wonder if Nix uses HTTP/2 there. I think with stream multiplexing, all requests could essentially fit in one pack of packets.
| 10:59:07 |
yorik.sar | *
I'd like to do further work to deduplicate queries for .narinfo and the like, since Nix already generates quite the network storm by firing them off in serial.
I wonder if Nix uses HTTP/2 there. I think with stream multiplexing, all requests could essentially fit in one pack of packets.
| 10:59:14 |