| 11 Mar 2025 |
 @hexa:lossy.network | commit 8c9755e515014f97a1985d19030ec90cb60785b4
Author: Martin Weinelt <hexa@darmstadt.ccc.de>
Date: Wed Jan 1 23:59:50 2025 +0100
home-assistant: use unstable jemalloc to match native dependencies
Otherwise home-assistant runs into import errors, e.g. on microvad
ImportError: /nix/store/ybjcla5bhj8g1y84998pn4a2drfxybkv-gcc-13.3.0-lib/lib/libstdc++.so.6: version `CXXABI_1.3.15' not found
diff --git a/modules/home-assistant/default.nix b/modules/home-assistant/default.nix
index 538c627..26a958e 100644
--- a/modules/home-assistant/default.nix
+++ b/modules/home-assistant/default.nix
@@ -20,7 +20,7 @@ in
./zigbee2mqtt.nix
];
- systemd.services.home-assistant.environment.LD_PRELOAD = "${lib.getLib pkgs.jemalloc}/lib/libjemalloc.so";
+ systemd.services.home-assistant.environment.LD_PRELOAD = "${lib.getLib unstable.jemalloc}/lib/libjemalloc.so";
services.home-assistant = {
enable = true;
| 17:13:45 |
| *  philipp is avoiding impurities by having home-assistant in a microvm.nix | 17:15:57 |
 @lynatic:catgirl.cloud | I somehow managed to have this problem while having this in a microvm already aaaa | 17:19:49 |
| @lynatic:catgirl.cloud | thanks, I'll try fixing my install to use that module declaration then | 17:20:25 |
| @hexa:lossy.network | are you also using jemalloc? | 17:20:41 |
| @hexa:lossy.network | or is your problem caused by sth else | 17:20:56 |
| @hexa:lossy.network | because you have not yet posted any error | 17:21:09 |
| @lynatic:catgirl.cloud | seems I just had a skill issue where my override only halfway worked (overrode the homeassistant packages but not the module) which caused a bunch of errors including the jemalloc one. got it to work now. | 17:53:04 |
| @hexa:lossy.network | systemd.services.home-assistant.environment = {
LD_PRELOAD = "${lib.getLib unstable.jemalloc}/lib/libjemalloc.so";
# https://github.com/jemalloc/jemalloc/blob/dev/TUNING.md
MALLOC_CONF = "background_thread:true,metadata_thp:auto,dirty_decay_ms:20000,muzzy_decay_ms:20000";
PYTHONMALLOC = "malloc";
};
| 17:54:05 |
| @hexa:lossy.network | is that I'm using these days fwiw | 17:54:09 |
| @hexa:lossy.network | hmmm | 17:55:00 |
| @hexa:lossy.network | why don't we have meta.mainLib 😄 | 17:55:06 |
| @hexa:lossy.network | and lib.getLib pkgs.jemalloc resolves to $out/lib/libjemalloc.so | 17:55:26 |
| @hexa:lossy.network | and lib.getLib' to arbitrary librarie names | 17:55:38 |
| @hexa:lossy.network | sorry, that is a bad idea 😄 | 17:55:49 |
|  @adam_neverwas:matrix.org removed their display name adam_neverwas. | 23:24:16 |
| 12 Mar 2025 |
|  @rosssmyth:matrix.org joined the room. | 00:40:29 |
 Sandro 🐧 | we have that, too and we bend backwards for avahi... | 10:32:38 |
| Sandro 🐧 | whats the difference? 10M? 50M?
I currently have this:
Memory: 308.4M (peak: 309.9M, swap: 2.6M, swap peak: 29.5M)
| 10:33:32 |
| Sandro 🐧 | also is that univerall? Do you think I could give this exact config to mailman? | 10:33:49 |
| Sandro 🐧 | Also should we set MALLOC_CONF for matrix, too? | 10:34:22 |
| Sandro 🐧 |
Note that it is recommended to combine the options with abort_conf:true which aborts immediately on illegal options.
Should we set that, too?
| 10:35:32 |
| Sandro 🐧 | but thanks for sharing that! Very much appreciated! | 10:35:52 |
| @hexa:lossy.network | hard to compare, given that our home-assistant setup likely differs a lot 🙂 | 10:52:49 |
| @hexa:lossy.network |
Memory: 521.8M (peak: 834.4M)
| 10:52:54 |
| @hexa:lossy.network | * Memory: 521.8M (peak: 834.4M)
| 10:53:07 |
|  basti n00b0ss joined the room. | 11:20:47 |
|  Lucy joined the room. | 11:20:56 |
| Sandro 🐧 | do you have metrics before you added that? | 12:14:41 |
| Sandro 🐧 | or maybe switch it off for a second and then see how it behaves? I will try it later on mine and see how it changes | 12:14:59 |
