RAM usage options (RPi 4B 8GB)

	A	B	C	D	E	F	G	H	I	J	K	L	M	N	O	P
1
2	Pool TICKER	Server Type	OS	N	--disable-delayed-os-memory-return	-I	-Iw	Is -A16m used?	-F	-H	-T	-S	Alternate Options	zram (cores - percent)	version	Observations

3	PGWAD	Relay	Ubuntu	4	Yes	0.3	600	Used	1.5	2500M	used	used				No significant advantage with memory. After 48 hours RAM usage is 90%
4		BP	Ubuntu	4	Yes	0.3	600	Used	1.5	2500M	used	used				Slot lenghts increased to 1.004 and never returned to 1sec. No significant advantage with memory or missed slots
5		BP	Ubuntu	2	yes	0	600	used	no	no	used	no				No missed slot for 12 Hours. Avg RAM usage < 74% After 12 hours progressively miss 5-6 slots every couple of hours.
6		Relay	Ubuntu	2	yes	0.3	600	used	1.5	2500M	no	used				Good option. RAM still moves to >87%
7		BP	Ubuntu	2	yes	0	600	used	no	3000M	used	no				Good for ALonzo No missed slot for 12 Hours. Avg RAM usage < 74% After 12 hours progressively miss 5-6 slots every couple of hours.
8		BP	Ubuntu	2	yes	0	600	used	1.5	3000M	no	no	-qb -qg1			Good stability. 12 hours no missed or <10. After that every 72 mins slots missed which is because of USB3.
9		Relay	Ubuntu	2	yes	0.3	600	used	1.5	3000M	no	used				Good option. for Alonzo% This is deprecated. Below option is better
10		Relay	Ubuntu	2	yes	0.3	600	used	1.5	3000M	no	used	-qb -qg1			Better than above for Alonzo% Set OUT to 10
11	QXT	Relay	Ubuntu	2	yes	0.3	600	used	1.5	2500M	no	used				Good option at the moment. RAM: 65%-75%. Low CPU (25% AVG). No dropouts all seems fine
12		Relay	Ubuntu	2	yes	no	no	no	no	no	no	no	-qg -qb -c			dropouts in TX & CPU Ticks
13		Relay	Ubuntu	4	yes	no	no	no	no	no	no	no	-qg -qb -c			Some SPO say are fine without problems. Dropouts in TX & CPU Ticks.
14		Relay	Ubuntu	2	yes	0	600	used	1.5	2500M	no	used				high RAM (60-85%) & CPU (54% AVG)
15		BP	Ubuntu	2	yes	0	600	used	1.2	2000M	used	no				good option at the moment. RAM between 60-75%. Low CPU (37% AVG). 11 hours with some (59) missed slots
16		BP	Ubuntu	2	yes	0.3	600	used	1.5	2500M	used	no				Disaster: 40 missed slots first hour, after worst
17		BP	Ubuntu	2	yes	0	600	used	1.2	1500M	used	no				in tests RAM: 58%-65% -> 6 missed slots (6 first hours)
18		BP	Ubuntu	2	yes	0	600	used	1.2	1000M	used	no				seems NO nice: RAM: 58%-65% -> 6 missed slots (from the beginning)
19		BP	Ubuntu	2	yes	0	600	used	1.5	1000M	used	no				Stable RAM: 54-69% CPU: 40%. 7 missed slots (2 hours)
20		BP	Ubuntu	2	yes	0	600	used	1.5	1500M	used	no				Stable RAM: 54-69% CPU: 40%. 6 missed slots (2 hours)
21		BP	Ubuntu	2	yes	0	600	used	no	no	used	no			1.32.1	Stable RAM: 54-69% CPU: 42%. 0 missed slots (12 hours). My preference to BP (1.27.0)
22		BP	Ubuntu	4	yes	0	600	used	no	no	used	no			1.32.1	Stable RAM: 54-69% CPU: 50%. 0 missed slots (11 hours)
23		BP	Ubuntu	4	yes	no	no	no	1.2	no	no	no	-gq1		1.32.1	RAM: 72% -> 85% testing. BEST
24		BP	Ubuntu	4	yes	no	no	-A64m	no	no	no	no	-gq1		1.33.0	Testing...
25		BP	Ubuntu	4	yes	0	no	no	no	no	no	no	-gq		1.35.3	Bad propagation speed
26		Relay	Ubuntu	4	yes	0.3	300	used	1.5	3G	yes	yes	-n4m -qg -qb -c			starting with 56% RAM, but lost data in Grafana -> Dropouts in TX & CPU Ticks.
27		Relay	Ubuntu	4	yes	0.3	300	used	1.5	3G	yes	yes	-n4m -qg -qb		1.30.1	97% RAM. It was better in 1.29.1
28		Relay	Ubuntu	4	yes	no	no	no	no	no	no	no	-M7000M -n4m -qg -qb -c		1.30.1	(75% -> RAM) Dropouts in TX & CPU Ticks.
29		Relay	Ubuntu	4	yes	no	no	no	no	no	no	no	-M7000M -n4m -qg -qb		1.30.1	(75% -> RAM) Dropouts in TX & CPU Ticks.
30		Relay	Ubuntu	4	yes	no	no	-A32m	1.5	no	yes	no	-M7000M -n4m		1.30.1	(68% -> RAM) Dropouts in TX & CPU Ticks.
31		Relay	Ubuntu	4	yes	no	no	no	1.2	no	no	no	-qg1 -n4m		1.35.3	testing
32		Relay	Ubuntu	4	yes	no	no	-A32m	1.5	no	yes	no	-n4m -Fd2		1.30.1	1.30.1 (100% CPU )
33		Relay	Ubuntu	4	yes	no	no	-A32m	1.5	no	yes	no	-n4m -K		1.30.1	1.30.1 (84% -> 98% RAM)
34		Relay	Ubuntu	4	yes	no	no	-A64m	1.2	no	no	no	-qg1 -n4m		1.35.3	Works fine. Best option (Limited IN Peers: 10)
35	CRYPO	Relay	Alpine OS	2	Used	0.3	600	Used	1.5	2500M	Not used	Used		Yes	1.31.1	Stable CPU and RAM (2% and 61.3%), good option for relay.
36		Relay	Ubuntu	4	Used	Not used	Not used	-A64m	1.2	Not used	Not used	Not used	-qg1 -n4m	Yes	1.34.1	RAM 96%, ZRAM 24%, CPU 5% (after 4 days) SOLID
37		Relay	Ubuntu	4	Not used	Not used	Not used	Not used	Not used	Not used	Not used	Not used		Yes	1.34.1	RAM 96%, ZRAM 75%, CPU 5% (after 4 days)
38		Bp	Alpine OS	2	Used	0	600	Used	1.2	2000M	Not used	Used		Yes	1.31.1	Stable CPU and RAM (1.6% and 61.4%), but missed 300 slots in 5 hours.
39		Bp	Alpine OS	2	Used	0	600	Used	Not used	Not used	Used	Not used		Yes	1.31.1	Not Stable
40		Bp	Ubuntu	4	Used	Not used	Not used	Not used	Not used	Not used	Used	Not used		Yes	1.34.1	RAM 90%, ZRAM 73%, CPU 4%
41		Bp	Ubuntu	4	Used	Not used	Not used	Not used	1.2	Not used	Not used	Not used	-gq1	Yes	1.34.1	Not Stable (500 missed slots per hour)
42		Bp	Ubuntu	4	Not used	Not used	Not used	-A64m	Not used	Not used	Not used	Not used	-c	Yes	1.34.1	Testing... No missed slots for the first 12 hours, then 150 missed slots every hour
43	SUDTI	Relay	Ubuntu	2	yes	0.3	600	used	1.5	2500M	no	used				RAM: 65%-70%. Low CPU (30% AVG). Best option more my relay
44	SUDTI	BP	Ubuntu	2	yes	0	600	used	no	no	used	no				RAM: <70% 0 missed slots (18 hours)
45	MINI1	BP	Ubuntu	2	yes	0	600	used	1.2	2500M	no	yes				RAM 70% after just 1h 30min. Worst performance in terms of lost slots (429 in 1.5h). Slot lenght constantly around 1.08
46		BP	Ubuntu	2	yes	0	600	used	no	no	used	no				RAM jumped immediately to 82% after restart. Missed slots are increasing in a steady way. Slot length always around 1.01
47		BP	Ubuntu	4	no	no	no	-A64m -c	no	no	no	no				Preferred config. RAM < 50%. No missed slots after 2h 15min. Slot lenght constantly at 1s.
48		Relay	Ubuntu	2	yes	-qg	-qb	-c	no	no	no	no				Good memory consuption <70%. Sometimes there are some dropouts of the relays.
49	Solpi	BP	Alpine OS	4	no	no	no	no	no	no	no	no				374 missed slots after 22h
50	Solpi	Relay	Ubuntu	4	no	no	no	no	no	no	no	no				RAM 90%+
51	PIADA	BP	MacOS	4	no	0.1	3600	-A32M	1.1	3500M	no	no	-AL128M -n4m -O3500M		1.33.0	BP node 1.33. Three relays attached - avg 9 OUT, 20 IN on relays. 1 block produced on this configuration.
52	PIADA	Relay	Ubuntu	2	no	0.1	3600	-A64M	1.1	3500M	no	no	-n4m -O3500M		1.33.1	1.33 - 85% mem usage - avg 9 OUT, 20 IN on relays - all tracing off except ChainDb and json logging in mainnet-config
53	ST4NA	Relay	Ubuntu	2	yes	0.3	600	used	1.5	2500M	no	used				Good option at the moment. RAM: 70%-75%. Low CPU (25% AVG).First boundry 300 slot missed and RAM 80% -90%
54	ST4NA	Relay	Ubuntu	2	yes	0.3	600	used	1.5	2500M	no	used
55	ANFRA	Relay	Raspbian 64bit	4	yes	0.3	300	used	1.5	3G	yes	yes	-n4m			Good for Relay 1.29.0
56	XORN	relay	Ubuntu	2	yes	0.3	600	yes	1.5	2500M	no	no	-qg -qb -c	4 - 25%		These are very good settings for a relay. Using between 38-50% RAM. Not recommending to use -c for a BP as it causes missed slots.
57		relay	Ubuntu	2	yes	0.3	600	yes	1.5	2500M	no	no	-qa -qb -qg -M4500M	4 - 25%		Good Settings. Predominantly below 4GB RAM.
58		relay	Ubuntu	2	yes	no	no	no	no	no	no	no	--nonmoving-gc	4 - 25%		The node runs smoothly. Responds to all prometheus requests. Eventually running out of memory and crashing. Looks like a memory leak.
59		relay	Ubuntu	3	yes	0.3	600	-A24m	1.5	2500M	no	no	-qg -qb -c	4 - 25%		Good settings. Usually between 40-60% RAM usage. In 2 weeks I ran out of memory once. Node crashed as a result.
60		relay	Ubuntu	3	yes	0.3	600	-A24m	1.5	2500M	no	no	-M3000M -qg -qb -c	4 - 25%		-M prevents heap from growing above 3G. Terminated with a Heap Exhausted exception.
61		relay	Ubuntu	3	yes	0.3	600	-A24m	1.5	2500M	no	no	-M4000M -qg -qb -c	4 - 25%		-M prevents heap from growing above 4G. Ran for 12 hours with between 38-42% RAM. It will terminate with Heap Exhausted exception if node requires larger than 4G heap size, which hasn't happened. CPU 5-25%.
62		relay	Ubuntu	4	yes	0.3	600	-A32m	1.5	2500M	no	no	-qa -qb -qg -M4500M	4 - 25%		Good settings for relay. Around 50% RAM.
63		relay	Ubuntu	4	yes	no	no	no	no	no	no	no	--nonmoving-gc	4 - 25%		The node runs smoothly. Responds to all prometheus requests. Eventually running out of memory and crashing. Looks like a memory leak. It doesn't run major GC very often. Adding -Iw RTS parameter doesn't change major GC runs.
64		relay	Ubuntu	4	yes	0.3	120	-A1.2M	1.2	2G	no	no	--nonmoving-gc -M7G	4 - 25%		Runs very smooth. Responds to all prometheus requests. Crashes a couple of times a week because not enough heap size. Takes between 60-70% RAM.
65		relay	Ubuntu	4	yes	0.3	120	-A1.1M	1.2	2G	no	no	--nonmoving-gc -M7G	4 - 25%		Runs very smooth. Responds to all prometheus requests. Crashes a couple of times a week because not enough heap size. Takes between 60-70% RAM.
66		relay	Ubuntu	4	yes	0.3	60	-A1M	1.1	3G	no	no	--nonmoving-gc -M7.5G	4 - 25%		Runs smoothly. Around 70% RAM. The node crashed once.
67		relay	Ubuntu	4	yes	0	no	-A1.2M	1.2	3G	no	no	--nonmoving-gc -n1m -O256M -qb0	4 - 25%		Runs very smooth. Responds to all prometheus requests. Crashes a couple of times a week because not enough heap size. Takes 70+% RAM.
68		relay	Ubuntu	4	yes	0.3	300	-A16M	1.2	3G	no	no	-qb -qg -M6G	4 - 25%		Been running this without issues for a couple of weeks now on 1.30.1. Process size is around 4.5GB. Good seetings for a relay, although the node does miss to respond to Prometheus requests around 10 times every 24h.
69		relay	Ubuntu	4	yes	0.3	600	-A32m	1.5	2500M	no	no	-M4000M -qa -qg1 -c	4 - 25%		These are very good settings for a relay memory wise. Usually using between 3-4 GB RAM. Predominantly below 4GB. Have been running this with 20 outgoing connections and no crashes for a week. This setting is causing heavy work when running a major GC to the point the node doesn't respond to prometheus.
70		relay	Ubuntu	4	yes	0.3	600	-A32m	1.5	2500M	no	no	-M4000M -qa -qg1 --nonmoving-gc	4 - 25%		Crashed with Heap Exhausted exception. Took 90% of RAM.
71		relay	Ubuntu	4	yes	0.3	600	-A32m	1.5	2500M	no	no	-qg -qb -c	4 - 25%		Running out of memory and crashing a couple of times a week on average.
72	OYSTR	BP	Ubuntu	2	yes	0.3	600	yes	1.5	2500M	no	no	-qa -qb -qg -M4500M			Causes missed slots every 10 minutes.
73		BP	Ubuntu	2	yes	no	no	yes	no	2500M	no	no	--nonmoving-gc			Runs smoothly. No missed slots. Ran out of RAM and crashed. Looks like a memory leak.
74		BP	Ubuntu	4	yes	0.3	600	-A32m	1.5	2500	no	no	-n4m			Causes missed slots every 10 minutes.
75		BP	Ubuntu	4	yes	0.3	600	-A32m	1.5	2500M	no	no	-qa -qb4 -qg4 -n4m -M4000M			Causes many missed slots every 10 mins.
76		BP	Ubuntu	4	yes	no	no	no	no	no	no	no				Missed slots every 75 minutes, which also coincides with RAM almost at 0.
77		BP	Ubuntu	4	yes	0.3	60	-A1M	1.1	3G	no	no	--nonmoving-gc -M7.5G			Causes 2 missed slots in a row once in a while. Around 70% RAM.
78		BP	Ubuntu	4	yes	0.3	120	-A1.2M	1.2	2G	no	no	--nonmoving-gc -M7G			Runs very smooth. Responds to all prometheus requests. No missed slots after 7h20m, when the node crashed and went into a restart loop. Takes between 60-70% RAM.
79		BP	Ubuntu	4	yes	0.3	no	-A1.2M	1.2	2G	no	no	--nonmoving-gc -M7G			Runs very smooth. Responds to all prometheus requests. Hasn't crashed one single time. Takes between 60-70% RAM. 2 missed slots in 2 hours.
80		BP	Ubuntu	4	yes	no	no	no	no	2500M	no	no	--nonmoving-gc			Ran out of RAM and crashed. No missed slots.
81		BP	Ubuntu	4	yes	0.3	300	yes	1.4	3000M	no	no	-M5000M -qn2			Causes missed slots every 5 minutes.
82		BP	Ubuntu	4	yes	0.3	600	-A32m	1.5	2500M	no	no	-qa -qg1 -M4000			Causes missed slots every 10 mins because of -Iw600. Tried to lower it to -Iw120, which caused missed slots every 2 mins.
83	SBR	relay	Ubuntu	1	no	no	no	no	no	no	no	no	-M7000M			Ram usage 85-88%. Uptime 4d without crashes. (Note, my hardware - Ampere Altra ARM 3ghz cpu, 8gb ram vps)
84		BP	Ubuntu	2	no	no	no	no	no	no	no	no	-M7000M			Ram usage 90%. Uptime 3d without crashes.
85	SRN	Relay	Ubuntu	4	yes	0	no	-A32m	1.5	no	yes	no	-M7000M -n4m	yes (8GB)		Stable. Restarts every 8 hours with systemd. -M ensures RAM consumption does not exceed limit of 7GB. 82% RAM consumption after 2 hours.
86	SRN	BP	Alpine OS	4	yes	0	no	-A32m	1.5	no	yes	no	-n4m	yes (8GB)		Stable. Does not automatically restart. Very little (about 5 or so) or no missed slots for 11 hours. GC comes in every 1 hour intervals after for about 10-15 slots an hour. Advised to restart after epoch boundary to reset RAM consumption. Introducing -M (if 7GB and below) will cause GC to start sooner than 11 hours. -n4m -A32m helps in minimising GC events. 86% RAM consumption after 26 hours.
87	ANTRIX	BP	Ubuntu	4	no	0		-A32M	1.2					yes (8GB)	1.33.0	70% RAM 0%ZRAM 24 missed slots in 1 day. Core crashed after 1.5 days
88	ANTRIX	Relay	Ubuntu	4	no	0		-A32M	1.2					yes (8GB)	1.33.0	70% RAM 0% ZRAM .. still testing
89	MINI	BP	Ubuntu	4	no	no	no	-A64m	no	no	no	no	-c	yes	1.33.0	No missed slots for the first 12h. Afterwards, like a swiss watch it starts missing 100 slots every hour.
90	MINI	Relay	Ubuntu	4	no	no	no	-A64m	no	no	no	no	-c	yes	1.33.0	Memory starts at 56% and increases over the course of 48h to 88% and stays there with ZRAM <1%. After 6h there are drop-outs (3 in a row) every hour.
91
92
93
94
95
96
97
98
99
100