From: admin@multipool•us
To: bitcoin-xt <bitcoin-xt@googlegroups•com>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Memory leaks?
Date: Fri, 16 Oct 2015 21:37:30 -0700 (PDT) [thread overview]
Message-ID: <1206de5a-e807-406e-9584-305a503d78ec@googlegroups.com> (raw)
In-Reply-To: <99C42DE7-814A-48F8-AB28-A5ADD77A9FD9@toom.im>
[-- Attachment #1.1: Type: text/plain, Size: 2890 bytes --]
I can do better than that:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
10625 ******** 20 0 41.310g 0.035t 51172 S 1.0 57.6 47:11.17
bitcoind
Any idea what's going on here?
$ cat /proc/10625/status|grep -i VM
VmPeak: 43647420 kB
VmSize: 43319932 kB
VmLck: 60 kB
VmPin: 0 kB
VmHWM: 38286252 kB
VmRSS: 38014300 kB
VmData: 43103812 kB
VmStk: 236 kB
VmExe: 8844 kB
VmLib: 194656 kB
VmPTE: 79932 kB
VmSwap: 0 kB
On Tuesday, October 13, 2015 at 2:56:15 PM UTC-7, Jonathan Toomim (Toomim
Bros) wrote:
>
> 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@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@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@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.
>
[-- Attachment #1.2: Type: text/html, Size: 7883 bytes --]
prev parent reply other threads:[~2015-10-17 4:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 21:56 Jonathan Toomim (Toomim Bros)
2015-10-13 22:49 ` odinn
2015-10-13 23:14 ` Jonathan Toomim (Toomim Bros)
2015-10-13 23:52 ` Dave Scotese
2015-10-14 0:08 ` Jonathan Toomim (Toomim Bros)
2015-10-14 0:25 ` Dave Scotese
2015-10-13 23:59 ` odinn
2015-10-14 7:22 ` Pavel Janík
2015-10-14 7:58 ` Tom Zander
2015-10-14 9:09 ` Mike Hearn
2015-10-14 15:19 ` odinn
2015-10-14 9:39 ` Wladimir J. van der Laan
2015-10-18 15:59 ` Jonathan Toomim
2015-10-19 19:17 ` Multipool Admin
2015-10-19 22:24 ` Multipool Admin
2015-10-20 10:12 ` Mike Hearn
2015-10-20 12:39 ` Jonathan Toomim
2015-10-21 3:01 ` Jonathan Toomim
2015-10-21 7:29 ` Tom Zander
2015-10-21 17:58 ` Jonathan Toomim
2015-10-22 16:06 ` Multipool Admin
2015-10-22 16:27 ` Jonathan Toomim
2015-10-22 17:01 ` Btc Drak
2015-10-23 6:41 ` Rusty Russell
2015-10-21 7:59 ` Ross Bennetts
2015-10-17 4:37 ` admin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1206de5a-e807-406e-9584-305a503d78ec@googlegroups.com \
--to=admin@multipool$(echo .)us \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=bitcoin-xt@googlegroups$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox