| 3 Nov 2024 |
|  Kiruya Momochi 百地希留耶 changed their display name from 百地希留耶 to Kiruya Momochi 百地希留耶. | 19:57:42 |
| 4 Nov 2024 |
|  @optimusgray:technogeek.ninja joined the room. | 01:18:36 |
|  rhousand joined the room. | 17:23:43 |
| 5 Nov 2024 |
|  liv [she/her] joined the room. | 20:31:27 |
| 6 Nov 2024 |
|  @seapat:matrix.org joined the room. | 13:45:46 |
 Scrumplex | Is there a way I can instruct Nix to prefer building locally over using remote builders?
I am on a x86_64-linux machine and I have a x86_64-linux remote builder. Currently Nix seems to prefer the remote builder, even though I have more cores (and performance per core) locally. The speed factor of the builder is 1 | 14:56:44 |
| Scrumplex | According to the documentation of nix.conf, the speed factor must be a positive integer, so I can't really do something like 0.5 | 14:57:09 |
| Scrumplex | * According to the documentation of nix.conf, the speed factor must be a positive integer, so I can't set it to something like 0.5 | 14:57:15 |
 flare | been using nixos for 2 years now and have only now heard of nix.conf. if anyone has experience on this it would be interesting to see that response | 15:00:44 |
 K900 | In reply to@flare:matrix.darkc0de.one
been using nixos for 2 years now and have only now heard of nix.conf. if anyone has experience on this it would be interesting to see that response Uhh, what | 15:00:58 |
| Scrumplex | * According to the documentation of nix.conf, the speed factor must be a positive integer, so I can't set it to something like 0.5 | 15:01:18 |
| Scrumplex | In reply to @flare:matrix.darkc0de.one
been using nixos for 2 years now and have only now heard of nix.conf. if anyone has experience on this it would be interesting to see that response I assume you have configured nix.conf just never directly. The options nix.settings.* will be used to generate /etc/nix/nix.conf on NixOS | 15:02:32 |
| K900 | In reply to@scrumplex:duckhub.io
Is there a way I can instruct Nix to prefer building locally over using remote builders?
I am on a x86_64-linux machine and I have a x86_64-linux remote builder. Currently Nix seems to prefer the remote builder, even though I have more cores (and performance per core) locally. The speed factor of the builder is 1 speedFactor isn't even considered for local builds | 15:02:39 |
| Scrumplex | In reply to @flare:matrix.darkc0de.one
been using nixos for 2 years now and have only now heard of nix.conf. if anyone has experience on this it would be interesting to see that response * I assume you have configured nix.conf, just never directly. The options nix.settings.* will be used to generate /etc/nix/nix.conf on NixOS | 15:02:42 |
| K900 | There's some weird heuristics | 15:02:53 |
| Scrumplex | In reply to @k900:0upti.me
speedFactor isn't even considered for local builds I feared this would be the case | 15:02:58 |
| Scrumplex | I think my biggest wish for Nix would be more dynamic allocation of resources. It would be great if Nix could somehow "look-ahead" and dynamically allocate more cores to build jobs.
Like let's say you are building a large closure and Nix will soon need to spend time building a single derivation that every remaining derivation depends on. It could just allocate all available cores to that derivation, while when building many derivations in parallel it could allocate a small amount of cores to not overwhelm the system | 15:06:57 |
| flare | In reply to @scrumplex:duckhub.io
I assume you have configured nix.conf, just never directly. The options `nix.settings.*` will be used to generate `/etc/nix/nix.conf` on NixOS i tend to just use the /etc/nixos/configuration.nix for my server deployments. I probably have a few settings in there though | 15:08:22 |
| flare | In reply to @scrumplex:duckhub.io
I think my biggest wish for Nix would be more dynamic allocation of resources. It would be great if Nix could somehow "look-ahead" and dynamically allocate more cores to build jobs.
Like let's say you are building a large closure and Nix will soon need to spend time building a single derivation that every remaining derivation depends on. It could just allocate all available cores to that derivation, while when building many derivations in parallel it could allocate a small amount of cores to not overwhelm the system i agree. especially after updating channels | 15:09:02 |
| 7 Nov 2024 |
|  @frumon:matrix.org left the room. | 12:27:57 |
| 8 Nov 2024 |
|  jschvz joined the room. | 02:56:26 |
| liv [she/her] changed their display name from olivia to liv [she/her]. | 04:17:38 |
| K900 | OK so what the fuck do people use for postgres monitoring now | 21:39:07 |
| K900 | pg_exporter is dead as hell | 21:39:14 |
| K900 | coroot-pg-agent looks to also be dead onw | 21:39:20 |
| K900 | * coroot-pg-agent looks to also be dead now | 21:39:26 |
| 9 Nov 2024 |
|  @signaleleven:signal-eleven.com joined the room. | 14:22:29 |
 Birhaman | Redacted or Malformed Event | 15:42:34 |
 steveej | K900: FWIW grafanna-alloy does use postgres_exporter so i'd expect it not to be fully dead :-D https://grafana.com/docs/alloy/latest/reference/components/prometheus/prometheus.exporter.postgres/ | 18:47:11 |
 magic_rb | In reply to @k900:0upti.me
OK so what the fuck do people use for postgres monitoring now telegraf maybe? they probably have a postgres module | 17:58:10 |
