V1.25.1 relay node ram usage very high - is that a bug?

@CryptoTorben I have disable tracer on one of my nodes will keep an eye on performance.

@COSDpool Thank you

1 Like

OK guys just an update over last 9 hours.
Relay1 has tracers enabled
Relay2 has tracers disabled
So despite the disadvantage of not being able to see transactions I probably would prefer to keep tracers disabled.
12

Thanks for your help guys

hey mate,
what is your CPU and RAM for this system?

@tsipou 2 vcpu 4gb ram

please upgrade
Screenshot 2021-03-01 at 10.37.36

but before you do this, without your last change for the tracers,
how was the health of the system?

@tsipou No issues
With tracers enabled ram was running 80% load and slowly climbing to 100%.
With tracers disabled RAM is running 60%. So far 7 hours and not climbing anywhere. may be tiny bit but I am still watching it. Will decide later.

1 Like

thank you mate, nice info to know

1 Like

i did "false " the TraceMempool on the relays…
but took my 1st relay 15 minutes without TXs, and the i did change it again as “true”

do you have an opinion?

Hey @tsipou yes man. when you do ‘false’ you disable trace that means you disable trace monitoring that is why you do not see them. That’s the main disadvantage of this work around.

1 Like

Final Update!
With 4 GB RAM on board it is does not matter if MempoolTracers enabled or disabled memory utilization will be slowly rising and eventually will result node to reboot. even if you use SWAP file. 4 GB RAM just not enough.
Solution: Use 8 GB RAM
My current node configuration 2 vCPU, 8GB RAM, MempoolTracers enabled running with no issues for almost 3 days.

1 Like

Minimum System Requirements

  • An Intel or AMD x86 processor with two or more cores, at 2GHz or faster
  • 8GB of RAM
  • 20GB of free storage
2 Likes

In fact, the minimum requirement is still 4gb by relay.

4GB of RAM (8GB for a relay or stake pool)

But with only 4gb…you are close to saturation and swap can’t save you.

Anyways, with small contracts coming, it will not be enought.

1 Like

I am sure this “bug” will be fixed in the next release

1 Like

Hello Anton_R,
you might try to also set
"minSeverity": "Error" in your mainnet-config.json.
Per default is is set to Information / Warning and then you get more stuff shown than you might need. If you set it to “Error” it will no longer print Info-Messages and Warning-Messages.

Hi tigrpool.com Thank you, good to know.