odinn [ARCHIVE] on Nostr: 📅 Original date posted:2015-10-13 📝 Original message:-----BEGIN PGP SIGNED ...

📅 Original date posted:2015-10-13
📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

You should compare this to having set up a node on a completely clean
computer. It would also help to know what operating system(s) you are
using for both the oldie and the freshie.

Also, dump your XT, is poo. Then try again, look at Core nodes on
your oldie and freshie. Watch them for a bit.

Cheers,

O

Jonathan Toomim (Toomim Bros) via bitcoin-dev:
> I just noticed that several of my running bitcoind processes were
> using around 3+ GB of RAM, even though the mempool itself seemed to
> be under control.
>
> XXXX at prime:~/bin$ ./bitcoin-cli getmempoolinfo { "size" : 1896,
> "bytes" : 37341328 }
>
> [total memory usage not shown -- I restarted bitcoind as soon as I
> noticed, and didn't copy it down from top]
>
> 37 MB mempool, >3 GB RAM usage. Normally, when there aren't a lot
> of unconfirmed txns floating around the network, memory usage is
> around 600 MB, so this is quite unusual.
>
> After restarting the process and letting it run for a few minutes,
> I get:
>
> PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+
> Command [###] [XXXX] 20 0 1402M 317M 49836 S 1.0 8.2
> 0:41.71 ./bitcoind -daemon
>
> XXXX at prime:~/bin$ ./bitcoin-cli getmempoolinfo { "size" : 1072,
> "bytes" : 670000 }
>
> 0.67 MB mempool, 317 MB RAM usage. Much more reasonable.
>
>
> Here's another node I'm running that has been online longer, before
> restarting:
>
> PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+
> Command [###] [XXXX] 20 0 4961M 3540M 11080 S 2.8 45.3
> 8h20:11 bin/bitcoind -daemon
>
> XXXX at feather:~$ bin/bitcoin-cli getmempoolinfo { "size" : 3045,
> "bytes" : 39656126 }
>
> 39 MB mempool, 3540 MB total memory usage. After restarting
> bitcoind, I see:
>
> [XXXX]@feather:~$ bin/bitcoin-cli stop Bitcoin server stopping
> [XXXX]@feather:~$ bin/bitcoind -daemon Bitcoin server starting
> [XXXX]@feather:~$ sleep 10; bin/bitcoin-cli getmempoolinfo { "size"
> : 39, "bytes" : 47037 }
>
>
> PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+
> Command [###] [XXXX] 20 0 1640M 247M 67960 S 0.0 3.2
> 0:05.17 bin/bitcoind -daemon
>
>
>
>
> Does anybody have any guesses where we might be leaking memory, or
> what is using the additional 2.4 GB? I've been using
> minrelaytxfee=0.00003 or similar on my nodes. Maybe there's a leak
> in the minrelaytxfee code path? Has anyone else seen something
> similar?
>
> This issue appears to happen both with Bitcoin Core 0.10.1 and with
> Bitcoin XT 0.11B.
>
>
>
> _______________________________________________ bitcoin-dev mailing
> list bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

- --
http://abis.io ~
"a protocol concept to enable decentralization
and expansion of a giving economy, and a new social good"
https://keybase.io/odinn
-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJWHYqAAAoJEGxwq/inSG8Cp8YIAJa9xWA+rNY9ZOTWjOEZGc7Q
IpXqpIyZprhEog6By/rQ7Te+xdUuaIZrMPESEoQIdMlDjRu7V2CWKGr1LbbDf2v9
A6nMhE19tazDSMAcqHlcuWRfpex3C5QD93Oo7h0QvioNLc8cseNsYzqvOW40vIFL
SPJOfor6IFLEi6/0t7OBhVyaXZdhI7XD1IDxeD67IOafCDwHgixFZWS4aCpz4axj
i4B8DNsVgDdeYI2STBiqnL9Sopdnc1q2CwC1ENszR+sCXwIB9vdPOtIjhtWGk1gi
f+/I8IUP/jn2xIjAGixjEePCIFLFV3kI+B6akH8+TsXB4G9C3zHEHTsfCrmLblg=
=VMV3
-----END PGP SIGNATURE-----