| 4 May 2026 |
 swarsel | yeah i will have to do that now, until now that only manifested in eval time taken which i did not care about, but now this needs fixing 😅 | 13:11:21 |
| 5 May 2026 |
| swarsel | well i looked into it a little and found that the biggest offender were a fer malformed lines that generated thousands of nftables rules for each wireguard peer - fixing that took it down from >90G to now about 20G. much, better, but still too much for my liking :p
all my cross node evaluations are already done once when filling my globals output - that iterates over all config and aggregates some global definitions. that is a mechanism that i really do not want to get rid of, i think it is super useful. also i thought that this kind of eval would not be very costly since nearly nothing needs to be accessed in the first place.
for my client pc config without any microvms, it takes me 9G - what is the memory usage for a usual nixosConfig for you guys? | 14:05:43 |
| swarsel | * well i looked into it a little and found that the biggest offender were a fer malformed lines that generated thousands of nftables rules for each wireguard peer - fixing that took it down from >90G to now about 20G. much, better, but still too much for my liking :p
all my cross node evaluations are already done once when filling my globals output - that iterates over all config and aggregates some global definitions. that is a mechanism that i really do not want to get rid of, i think it is super useful. also i thought that this kind of eval would not be very costly since nearly nothing needs to be accessed in the first place.
for my client pc config without any microvms, it takes me 9G - what is the memory usage for a usual nixosConfig for you people? | 14:07:59 |
| swarsel | * well i looked into it a little and found that the biggest offender were a fer malformed lines that generated thousands of nftables rules for each wireguard peer - fixing that took it down from >90G to now about 20G (that surprised me a lot!). much, better, but still too much for my liking :p
all my cross node evaluations are already done once when filling my globals output - that iterates over all config and aggregates some global definitions. that is a mechanism that i really do not want to get rid of, i think it is super useful. also i thought that this kind of eval would not be very costly since nearly nothing needs to be accessed in the first place.
for my client pc config without any microvms, it takes me 9G - what is the memory usage for a usual nixosConfig for you people? | 14:13:31 |
| swarsel | * well i looked into it a little and found that the biggest offender were a fer malformed lines that generated thousands of nftables rules for each wireguard peer - fixing that took it down from >90G to now about 20G (that surprised me a lot!). much, better, but still too much for my liking :p
all my cross node evaluations are already done once when filling my globals output - that iterates over all config and aggregates some global definitions. that is a mechanism that i really do not want to get rid of, i think it is super useful. also i thought that this kind of eval would not be very costly since nearly nothing needs to be accessed in the first place. the evaluation of globals by itself (which is around 35 configs I guess) takes around 4G, which seems reasonable?
for my client pc config without any microvms, it takes me 9G - what is the memory usage for a usual nixosConfig for you people? | 14:44:24 |
| 18 Nov 2023 |
|  spacesbot - keeps a log of public NixOS channels joined the room. | 14:08:18 |
| spacesbot - keeps a log of public NixOS channels | 15:00:22 |
| 19 Nov 2023 |
 Krezzlu | Redacted or Malformed Event | 09:46:57 |
|  ZXGU joined the room. | 10:58:29 |
| 20 Nov 2023 |
|  phaer changed the room topic to "nixos.at - Nix(OS) meetups in Graz, Vienna and elsewhere in Austria; in German and English." from "nixos.at - Nix(OS) meetups in Graz, Vienna and elsewhere in Austria; in German and English (Formerly #nixos-vienna) ". | 12:49:24 |
| 3 Dec 2023 |
|  hakmark joined the room. | 10:05:29 |
| 7 Dec 2023 |
|  Rasmus changed their profile picture. | 10:29:10 |
| 13 Dec 2023 |
|  admu joined the room. | 07:11:25 |
| admu changed their display name from adam mccartney to admu. | 07:12:00 |
| 25 Dec 2023 |
|  ruru4143 changed their display name from ruru4143 to ruru[📞:4143]. | 13:38:28 |
|  xro changed their display name from xro to xrotest. | 19:51:26 |
| xro changed their display name from xrotest to xro2. | 19:51:48 |
| xro changed their display name from xro2 to xro. | 19:55:32 |
| 26 Dec 2023 |
|  domih changed their profile picture. | 11:03:55 |
| 27 Dec 2023 |
|  jstsmthrgk changed their display name from jstsmthrgk to jstsmthrgk [DECT 5651]. | 09:26:09 |
| 1 Jan 2024 |
| ruru4143 changed their display name from ruru[📞:4143] to ruru4143. | 00:47:46 |
| 2 Jan 2024 |
| jstsmthrgk changed their display name from jstsmthrgk [DECT 5651] to jstsmthrgk. | 11:40:28 |
| 7 Jan 2024 |
| Rasmus changed their profile picture. | 16:35:11 |
| 22 Jan 2024 |
|  rettetdemdativ joined the room. | 13:18:42 |
| 5 Feb 2024 |
|  Martin Schwaighofer joined the room. | 18:49:26 |
| ruru4143 changed their display name from ruru4143 to ruru4143 [chaos.jetzt, realraum/graz]. | 22:00:42 |
| 6 Feb 2024 |
| ruru4143 changed their display name from ruru4143 [chaos.jetzt, realraum/graz] to ruru4143. | 10:14:13 |
|  bbenno joined the room. | 10:58:42 |
| 14 Feb 2024 |
| Martin Schwaighofer changed their display name from Martin Schwaighofer@FOSDEM to Martin Schwaighofer. | 12:28:44 |
| 18 Feb 2024 |
|  Finn Landweber joined the room. | 08:40:12 |
