From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id D84EB90 for ; Tue, 13 Oct 2015 23:52:08 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 6F6B7F3 for ; Tue, 13 Oct 2015 23:52:07 +0000 (UTC) Received: by wijq8 with SMTP id q8so55721869wij.0 for ; Tue, 13 Oct 2015 16:52:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=uTbUsU2eR0YsqOeMmIHt5ATFRBaMz/uvGg0inXiSg+8=; b=bLCADJ4J4kSJTd4x7X381hHJsylsDpglWVwicbNwe9JQteOsvwyuFB/geE5aLfwu/N VrYPPPN6uYo5ZBAieF6Y5iYK8SP9/P4leRDkvUq00/1dZS0ZUByu1kKIZDTPj+AR/a0v b0IWa8wFDBNWhyMWsf0CkLem4/rX4H0ETeLWgSuA2YmMXFvIOMpGwNNCFZ9KZLpJlT9J PIDa/IBta7Hr0SW53XC9b50oWA6tzBWTm9GVhij/D8/T9Vp8c3ShJy+NJCf1QAgusT8X IjXvDXI/YhNKwD1gpC7Y5r/onY0l8LY96Hh42mFX1wpcv3enRzgw3U47kUCkaFwj20uj lETA== MIME-Version: 1.0 X-Received: by 10.180.188.169 with SMTP id gb9mr25323342wic.72.1444780325849; Tue, 13 Oct 2015 16:52:05 -0700 (PDT) Sender: dscotese@gmail.com Received: by 10.27.211.132 with HTTP; Tue, 13 Oct 2015 16:52:05 -0700 (PDT) In-Reply-To: <468C1911-C504-4622-BCC8-FF0AAB17E874@toom.im> References: <99C42DE7-814A-48F8-AB28-A5ADD77A9FD9@toom.im> <561D8A81.2020109@riseup.net> <468C1911-C504-4622-BCC8-FF0AAB17E874@toom.im> Date: Tue, 13 Oct 2015 16:52:05 -0700 X-Google-Sender-Auth: -U2fFAK1V-X7UAeaVIbNMJkEXkw Message-ID: From: Dave Scotese To: bitcoin-xt Content-Type: multipart/alternative; boundary=001a11c26bb819d43e05220522bd X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: Bitcoin Dev Subject: Re: [bitcoin-dev] Memory leaks? X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Oct 2015 23:52:09 -0000 --001a11c26bb819d43e05220522bd Content-Type: text/plain; charset=UTF-8 { "size" : 1085, "bytes" : 16151768 } It has been running about a day. I'll report tomorrow too. This is a Windows 8.1 box. 16 million divided by 1085 transactions is almost 15Kb per transaction = unlikely, right? On Tue, Oct 13, 2015 at 4:14 PM, Jonathan Toomim (Toomim Bros) wrote: > > On Oct 13, 2015, at 3:49 PM, odinn > 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? > > -- > You received this message because you are subscribed to the Google Groups > "bitcoin-xt" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to bitcoin-xt+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- I like to provide some work at no charge to prove my value. Do you need a techie? I own Litmocracy and Meme Racing (in alpha). I'm the webmaster for The Voluntaryist which now accepts Bitcoin. I also code for The Dollar Vigilante . "He ought to find it more profitable to play by the rules" - Satoshi Nakamoto --001a11c26bb819d43e05220522bd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


{
"size" : 1085,
&q= uot;bytes" : 16151768
}

= It has been running about a day.=C2=A0 I'll report tomorrow too.=C2=A0 = This is a Windows 8.1 box.

16 mi= llion divided by 1085 transactions is almost 15Kb per transaction =3D unlik= ely, right?


On Tue, Oct 13, 2015 at 4:14 PM, Jonathan= Toomim (Toomim Bros) <j@toom.im> wrote:

On Oct 13, 2015, a= t 3:49 PM, odinn <odinn.cyberguerrilla@riseup.net> wrote:

Signed PGP p= art
It would also = help to know what operating system(s) you are
using for both the oldie a= nd 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 consumpti= on 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 com= pletely 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 tryi= ng 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 becaus= e the issue appears to affect both forks. Let's keep blocksize and gove= rnance debates to their own threads, please.

Repea= ting request: Has anyone else seen something similar? Can you report your m= empool size and total bitcoind resident set size for your running full node= s?

--
You received this message because you are subscribed to the Google Groups &= quot;bitcoin-xt" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoin-xt+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
I like to provide some work at no cha= rge to prove my value. Do you need a techie?=C2=A0
I own Litmocracy and Meme Racing (in alpha).
I= 'm the webmaster for The Voluntaryist which now accepts Bitcoin.
I also code for = The Dollar Vigila= nte.
"He ought to find it more profitable to play by the rules&= quot; - Satoshi Nakamoto
--001a11c26bb819d43e05220522bd--