2020-04-05 12:34:17
my node uses 17,5GB of resident memory at the moment, is this expected?
Rotonen
2020-04-05 12:34:41
and the pool with no users uses 5GB
Rotonen
2020-04-05 12:35:53
the essentially idle channel node also uses some 400MB
Rotonen
2020-04-05 12:40:10
restarted processes and seeing where they climb up to
Rotonen
2020-04-05 12:41:16
IMO going above 3G required memory use for the node disqualifies way too many people from hosting one
Rotonen
2020-04-05 12:56:08
seems to have stabilized at 2G for the pool, 1G for the node and 600M for the channel node
Rotonen
2020-04-05 17:22:58
shouldn't need that much, but depending on jvm settings it will of course use a ton
Fireduck
2020-04-05 19:27:35
i simply `java -jar` those
Rotonen
2020-04-05 19:27:46
`openjdk version "11.0.5" 2019-10-15`
Rotonen
2020-04-05 19:30:14
the pool now takes over 4G again
Rotonen
2020-04-05 19:30:23
is that the GC just being lazy as the system has memory?
Rotonen
2020-04-05 19:32:28
as i'm not setting a heap size, that would need to be non-heap space?
Rotonen
2020-04-05 21:46:21
I'll do some testing. In general, if it doesn't run with -Xmx2g I would consider that a defect.
But without that arg, the jvm tends to be a bit lazy in the GC and just doesn't clean up
Fireduck
