| 29 Dec 2023 |
 hexa | for which it determined the size by itself? | 19:53:03 |
 @joepie91:pixie.town | there's something like node --v8-flags that should show you the relevant flags in your Node/V8 version | 19:53:17 |
| @joepie91:pixie.town | (not sure if that's exactly the right parameter) | 19:53:29 |
| hexa | ok | 19:53:39 |
| @joepie91:pixie.town | In reply to @hexa:lossy.network
for which it determined the size by itself? it's set to some default, I don't remember how much, couple gigs | 19:53:47 |
| @joepie91:pixie.town | ah it seems that newer Node/V8 versions just have a --max-heap-size flag | 19:54:35 |
| @joepie91:pixie.town | so try --max-heap-size 8G or so and see if that works :p | 19:54:50 |
| hexa | --max-heap-size (max size of the heap (in Mbytes) both max_semi_space_size and max_old_space_size take precedence. All three flags cannot be specified at the same time.)
type: size_t default: --max-heap-size=0
--initial-heap-size (initial size of the heap (in Mbytes))
type: size_t default: --initial-heap-size=0
| 19:55:09 |
| @joepie91:pixie.town | right so I guess 8096 is the right value then | 19:55:41 |
| hexa | 0 sounds like autopilot or inf | 19:55:43 |
| @joepie91:pixie.town | for the max | 19:55:47 |
| @joepie91:pixie.town | hm | 19:55:55 |
| @joepie91:pixie.town | that was not historically the case | 19:55:59 |
 Wanja Hentze | I remember passing that to npm at some point | 19:56:00 |
| hexa | right, but cached/buffer should be available for allocation | 19:56:02 |
| @joepie91:pixie.town | I think that just means that it uses the (now hidden?) space_size params? | 19:56:12 |
| hexa | too many params | 19:56:28 |
| @joepie91:pixie.town | I would just try setting the heap size to 8G and seeing if the issue reoccurs | 19:56:46 |
| hexa | then I need to allocate more memory to the machine | 19:56:58 |
| hexa | it currently has 8G, which becomes 7.7G in the guest | 19:57:10 |
| hexa | wondering what resources element spent on the bridge infra | 19:57:38 |
| hexa | can't listen to maja göpel and do this tbh 😄 | 19:59:30 |
| hexa | * can't listen to maja göpel and deal with this tbh 😄 | 19:59:46 |
| @joepie91:pixie.town | not sure why this would necessitate giving the machine more memory | 20:00:11 |
| @joepie91:pixie.town | it's a max heap size, not a fixed heap size | 20:00:17 |
| Wanja Hentze | also, VMs can still both overcommit and swap, right? | 20:05:06 |
| Wanja Hentze | In reply to @joepie91:pixie.town
it's a max heap size, not a fixed heap size supposedly it really did run into the limit | 20:05:47 |
| hexa | overcommit with ballooning? | 20:06:16 |
| hexa | and swap only if I added some | 20:06:20 |
| hexa | often enough heap space is locked, so I'm doubtful this would help | 20:06:43 |
