From: "Jonathan Toomim (Toomim Bros)" <j@toom.im>
To: odinn <odinn.cyberguerrilla@riseup.net>
Cc: bitcoin-dev@lists.linuxfoundation.org, bitcoin-xt@googlegroups.com
Subject: Re: [bitcoin-dev] Memory leaks?
Date: Tue, 13 Oct 2015 16:14:46 -0700 [thread overview]
Message-ID: <468C1911-C504-4622-BCC8-FF0AAB17E874@toom.im> (raw)
In-Reply-To: <561D8A81.2020109@riseup.net>
[-- Attachment #1.1: Type: text/plain, Size: 1539 bytes --]
On Oct 13, 2015, at 3:49 PM, odinn <odinn.cyberguerrilla@riseup.net> wrote:
> Signed PGP part
> It would also help to know what operating system(s) you are
> using for both the oldie and the freshie.
Linux feather 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 (2015-08-04) x86_64 GNU/Linux
Linux server 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64 GNU/Linux
Linux prime 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u2 x86_64 GNU/Linux
This excessive memory consumption was seen on 3 machines, all of which run Debian. All three machines run p2pool as well as bitcoind. Two run XT, one runs Core.
>
> You should compare this to having set up a node on a completely clean
> computer.
I can't afford to do that. All of the servers I have are being used for something. Also, I'm not sure what it is you're trying to test for with that suggestion. The numbers I'm reporting are for bitcoind's resident set, not for the whole server's memory usage. I don't see how other processes running on the same machine are relevant unless you are suggesting that RPC calls (e.g. getblocktemplate) might be somehow responsible.
>
> Also, dump your XT, is poo.
Not relevant. I addressed this message to both the Core and XT lists because the issue appears to affect both forks. Let's keep blocksize and governance debates to their own threads, please.
Repeating request: Has anyone else seen something similar? Can you report your mempool size and total bitcoind resident set size for your running full nodes?
[-- Attachment #1.2: Type: text/html, Size: 3401 bytes --]
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 496 bytes --]
next prev parent reply other threads:[~2015-10-13 23:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 21:56 [bitcoin-dev] Memory leaks? Jonathan Toomim (Toomim Bros)
2015-10-13 22:49 ` odinn
2015-10-13 23:14 ` Jonathan Toomim (Toomim Bros) [this message]
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
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=468C1911-C504-4622-BCC8-FF0AAB17E874@toom.im \
--to=j@toom.im \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=bitcoin-xt@googlegroups.com \
--cc=odinn.cyberguerrilla@riseup.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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