 | nixos-at | 83 Members |
| vienna.nix.ug - Nix(OS) meetups in Vienna nixos.at - Nix(OS) meetups in Graz & elsewhere in Austria | 28 Servers |
| nixos-at | 83 Members |
| vienna.nix.ug - Nix(OS) meetups in Vienna nixos.at - Nix(OS) meetups in Graz & elsewhere in Austria | 28 Servers |
| Sender | Message | Time |
|---|---|---|
| 18 Mar 2026 | ||
 fschn90 | reminder: tomorrow's our next meetup: https://vienna.nix.ug/#2026-03-19-meetup 18h at Wirkstätte, Khunngasse 6-8, 1030 Wien looking forward! 🦦 | 08:43:08 |
| 19 Mar 2026 | ||
 BPub | Hi every1! I'll fetch a few snacks again from the supermarket before we meet. Like Soletti and nuts and a few vegetable snacks. Coffee and tea is always there at the Wirkstätte. If anyone else wants to fetch some drinks or sweets, or smth. else I suggest dropping a message here. I'll be there at aboyt 5pm if someone wants to be early | 15:01:57 |
| BPub |  Download Das ist der Eingang | 16:27:41 |
 swarsel | are ypu guys still around? i would arrive probably at around 2130 :) | 19:42:18 |
| swarsel | * are you guys still around? i would arrive probably at around 2130 :) | 19:42:28 |
| fschn90 | hi, yes | 19:57:08 |
| fschn90 | currently 7 people | 19:57:14 |
| 23 Mar 2026 | ||
| fschn90 | Save the date: NixOS Vienna — April 2026 Meetup (homepage post will follow) 📅 Thursday, April 23, 2026 at 18:00 📍 Wirkstätte, Khunngasse 6-8, 1030 Wien looking forward! | 15:16:48 |
| 28 Mar 2026 | ||
 @jan4843:matrix.org left the room. | 11:13:45 | |
| 13 Apr 2026 | ||
 Tanja (she/her) removed their profile picture. | 14:20:19 | |
| 18 Apr 2026 | ||
| fschn90 | Quick reminder: see you next week thurdsday 18h at Wirkstätte in Vienna :) | 21:09:14 |
| 21 Apr 2026 | ||
| BPub | For Thursday: Coffee and tea are always there. And I'll bring the usual healthy snacks again. (cherry tomatoes, cucumber, bell pepper, stuff like that). There are some sweets and beer left from last time iirc. I'll put the beer in the fridge in the afternoon. The slow internet fixed itself btw. Seems to have been a bad Magenta day last time. :) | 14:08:51 |
| BPub changed their profile picture. | 14:10:32 | |
| 23 Apr 2026 | ||
 phaer | Looking forward to see (some of) you later today! Lots of nice new features coming up for 26.05 (systemd-in-initrd by default, optional nixos tests with nspawn containers instead of qemu, maybe even boot counting as well - and that's just from the top of my head). Happy to chat about all of them! Maybe we could do try a tiny bit of program for the next meetup again? e.g. lightning talks on new or old stuff or a small set of issues we could try to tackle together? Lets discuss :) | 10:15:39 |
| 27 Apr 2026 | ||
 Ninja joined the room. | 14:57:25 | |
| 29 Apr 2026 | ||
 put101xyz joined the room. | 10:07:00 | |
| 30 Apr 2026 | ||
 Jaan joined the room. | 21:26:51 | |
| 1 May 2026 | ||
| swarsel | what are the best ways to get insight on where the memory footprint of an evaluation comes from? i noticed that my builder constantly ran out of memory when trying to build one of my configurations - I then built it locally and noticed that it takes 96G to evaluate 😅 the machine has 20 microvm guests which probably accounts for some of this, but I still think that I must be using some antipatterns that increase it to such amounts ^^ | 07:10:51 |
 ---m--- | Redacted or Malformed Event | 12:30:50 |
| 4 May 2026 | ||
| phaer | The "Zero Hydra Failures" campaign for the upcoming 26.05 has started: https://github.com/NixOS/nixpkgs/issues/516381 🎉 It's a shared effort to try and squash as many build errors & other bugs as possible, during the release process. 🐛 The issue description provides a nice intro as well as technical details on how to find staff to work on. I also found https://zh.fail/ useful. 📉 Posting this as there were people motivated to hack together at the May meetup. I personally will be on vacation this time 🏝️ Have fun! :) | 13:03:23 |
| phaer | the simplest, most primitive thing that comes to mind is NIX_SHOW_STATS=1 which lets nix print eval stats, including memory usage. A good start to confirm whether it's microvms, could be to eval each of them separately, and/or the toplevel closure without the vms (e.g. commented-out for a moment). | 13:06:24 |
| phaer | a classic There's some support for profiling, but IMO they are mostly useful for speed. I personally don't find the profile helps me much to understand memory evals | 13:09:10 |
| swarsel | yeah NIX_SHOW_STATS is where i got the number from (totalBytes) - I think the issue is that I am cross-referencing other nodes in nearly each one of them - i am not sure how it affects the whole closure, but could be that each microvm in essence then has to eval itself + all other nodes? | 13:09:36 |
| swarsel | * yeah NIX_SHOW_STATS is where i got the number from (totalBytes) - I think the issue is that I am cross-referencing other nodes in nearly each one of them - i am not sure how it affects the whole closure, but could be that each microvm in essence then has to eval itself + all other nodes? i guess that would scale exponentially. interestingly, when i removed a single microvm, i noticed nearly no difference in the memory usage | 13:10:22 |
| phaer | Ah, i was about to write: yes, cross-references between nixos closures should be avoided as much as possible, if you care about memory usage IMO. | 13:10:28 |
| 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 |