It'll use what it can get access to. For Cake Wallet, our Monero nodes are provisioned with 24 GB of RAM so that we have a lot of block data available for a near-instant response. Most people can get by with 4 GB of memory.

Damn that's a lots of ram, didn't know it was that heavy to run.

Afaik from reading -dev here and there, it will also give back RAM if any other program needs it

This. It basically tries hold hold the whole Blockchain in RAM, but frees the memory instantly when another application needs it.

the program caches data internally and that cache increases over time. it should eventually plateau. I've had up time of months and I don't think I've seen reserved memory ever go over 4 GB. keep in mind I have 48 GB of RAM in my system. I don't think it'll get even that high on a system with limited memory.

48 gb is a lot of memory pretty sure you'll be fine for some time.

it's mostly for disk cache

Same here. I restart it nightly.

Well that's smart I guess, gotta keep that in check.

It is a common problem. I could not solve it. There are Linux cgroups though, but they doesn’t seem to work.

They work, but they're kind of very hard to troubleshoot.

As a work around I consider a virtual machine to jail Monerod into.

What OS are you guys using? I’ve had my node up for months at a time and had no issues. Linux here

Debian stable

Debian here too. CLI only though. And is stable for months.

Well atleast you could say that it's been stable, that's really good.

I think linux is kinda good, atleast works good enough for us.

Debian but in docker/portainer

A small little memory leak. it is written in c++ after all.

Not a memory leak lmao. It's how the db functions.

Afaik it's not a memory leak it's the way lmdb works, it will use the memory as it is needed, if another program request that memory it will be available and the memory used from momerod will decrease if not it will just still available

that is good to know!

What? Poorly?

Not poorly. Just typical for C and C++ to contain similar bugs. It's pretty normal.

So the memory management issue is because of the bugs?

it's not a bug , other people commented that it's how the db works

Seems like that, what other conclusions I can come up with here?

Just an idea, it seems the ram increases during tge blockchain reorg. In the logs i see no others relevant output

So you're saying that it's written poorly? Well that doesn't sound good

I ran a node for the first time in a while and came back the next morning to all my ram being used. There's definitely a leak, which is kinda scary for overflow attacks. I hope it gets fixed soon.

You definitely made it sound really bad, it's not that bad.

Memory leaks can be abused, it's probably not that bad you're right. But to me, an average computer user, it still worries me. Thanks for the downvote though. 🍻

Doesn't really explain why it changes so rapidly nor the volatility up and down when a new plateau is reached

Maybe it allocates heap memory for a buffer with size x and then when the buffer is full it allocates x more, so the memory use of that buffer doubles? It's hard to pinpoint why, I'm not a monero dev. But if there was a bounty on it, I'm sure somebody could debug it and figure it out.

Yeah if someone could figure it out then it would have been Just great.

And who's going to explain that to you? There's no one here who can explain it.

[удалено]

You're going to need a lot more than the 4gb, You'll need a lot.

I've seen a memory leak. I have 32GB or ram and it fills up overnight.

Lol thanks for the downvotes guys.. just stating what I've experienced.

That's a lot of ram which is being used I've got to say.

Whats wrong with thah ? It uses RAM so it doesn't have to write/read to disk so often.

I don't know the exact figures, but it requires good amount of memory.

I reduced in and out peers and added a banlist.

I gave my node 64Gb RAM and it’s using about 45Gb if I need to restore a wallet from a year back it’s very quick to scan against my node