1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
|
Return-Path: <j@toom.im>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 0D5E2282
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 13 Oct 2015 23:14:53 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id D0EBF128
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 13 Oct 2015 23:14:51 +0000 (UTC)
Received: from [192.168.1.190] (63.135.62.197.nwinternet.com [63.135.62.197]
(may be forged)) (authenticated bits=0)
by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id t9DNElMG016864
(version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT);
Tue, 13 Oct 2015 16:14:48 -0700
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed;
boundary="Apple-Mail=_50135523-1769-4820-9F8D-7D55191555DD";
protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: "Jonathan Toomim (Toomim Bros)" <j@toom.im>
In-Reply-To: <561D8A81.2020109@riseup.net>
Date: Tue, 13 Oct 2015 16:14:46 -0700
Message-Id: <468C1911-C504-4622-BCC8-FF0AAB17E874@toom.im>
References: <99C42DE7-814A-48F8-AB28-A5ADD77A9FD9@toom.im>
<561D8A81.2020109@riseup.net>
To: odinn <odinn.cyberguerrilla@riseup.net>
X-Mailer: Apple Mail (2.1878.6)
X-Sonic-CAuth: UmFuZG9tSVauTgB6Llf24R7sFmL6dgmSWMM0VqTvj9anCFREyVLvs46kHVSInAs4n5jO78QY8OZ5jBUmtApd8xYyxmEOEicR
X-Sonic-ID: C;9AdpMgBy5RGLsOK7sH9FTg== M;2D8BMwBy5RGLsOK7sH9FTg==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,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@lists.linuxfoundation.org, bitcoin-xt@googlegroups.com
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 <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Oct 2015 23:14:53 -0000
--Apple-Mail=_50135523-1769-4820-9F8D-7D55191555DD
Content-Type: multipart/alternative;
boundary="Apple-Mail=_A5AB63CA-D78D-4A79-8DBB-BFEBC5376042"
--Apple-Mail=_A5AB63CA-D78D-4A79-8DBB-BFEBC5376042
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=windows-1252
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.
>=20
> 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.
>=20
> 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?
--Apple-Mail=_A5AB63CA-D78D-4A79-8DBB-BFEBC5376042
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=windows-1252
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><br><div><div>On Oct 13, 2015, at 3:49 PM, odinn =
<<a =
href=3D"mailto:odinn.cyberguerrilla@riseup.net">odinn.cyberguerrilla@riseu=
p.net</a>> wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;"><fieldset style=3D"padding-top: 10px; =
border: 3px solid rgb(204, 204, 204); padding-left: 20px; position: =
static; z-index: auto;"><legend style=3D"font-weight: bold;">Signed PGP =
part</legend><div style=3D"padding-left: 3px;">It would also help to =
know what operating system(s) you are<br>using for both the oldie and =
the =
freshie.<br></div></fieldset></div></blockquote><div><br></div><div><div><=
div style=3D"margin: 0px; font-family: 'Andale Mono'; color: rgb(41, =
249, 20); background-color: rgb(0, 0, 0); position: static; z-index: =
auto;">Linux feather 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 =
(2015-08-04) x86_64 GNU/Linux</div></div><div><div style=3D"margin: 0px; =
font-family: 'Andale Mono'; color: rgb(41, 249, 20); background-color: =
rgb(0, 0, 0);">Linux server 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 =
x86_64 GNU/Linux</div></div><div><div style=3D"margin: 0px; font-family: =
'Andale Mono'; color: rgb(41, 249, 20); background-color: rgb(0, 0, =
0);">Linux prime 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u2 x86_64 =
GNU/Linux</div></div><div><br></div><div>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.</div><div><br></div><div><blockquote type=3D"cite"><fieldset =
style=3D"padding-top: 10px; border: 3px solid rgb(204, 204, 204); =
padding-left: 20px; position: static; z-index: auto;"><div =
style=3D"padding-left: 3px;">You should compare this to having set up a =
node on a completely =
clean<br>computer.</div></fieldset></blockquote></div><div><br></div><div>=
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.</div><div><br></div><div><blockquote type=3D"cite"><fieldset =
style=3D"padding-top: 10px; border: 3px solid rgb(204, 204, 204); =
padding-left: 20px; position: static; z-index: auto;"><div =
style=3D"padding-left: 3px;">Also, dump your XT, is =
poo.</div></fieldset></blockquote></div><div><br></div><div>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.</div><div><br></div><div>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?</div></div></div></body></html>=
--Apple-Mail=_A5AB63CA-D78D-4A79-8DBB-BFEBC5376042--
--Apple-Mail=_50135523-1769-4820-9F8D-7D55191555DD
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQEcBAEBCgAGBQJWHZBnAAoJEIEuMk4MG0P1B0gH/RIxfFX6AZEx/J9e5+821IWw
ebw+uryKeqrIaI4y7qMLv/kXadMT+9Y9DWZzxF+n4WZlz0uGpBiNvVH1h3Sm5iN5
DMD5+YUDdUbPVuiNpStlwpZWwIk3WRJrK45lDylNqs9OEvg1SX50uKLmi4Rlbmbn
pRxYcNhV659Odv3py2UWGIZonGYHKiqKXTyszUt/G1ESAJPK/Q4o/HKDhVvcG945
K3leDnSIExglmmj7LYOq67ewGRDSBfs3tEskTks7ksXK+fUtS/EpFbqlLWWUrvqZ
rQV8ZJP/z6tM7ZIQWhtFTwsjZqewAvDpR0HFCO+3GoL9QbutA5atm3lXE+89S/A=
=9xX7
-----END PGP SIGNATURE-----
--Apple-Mail=_50135523-1769-4820-9F8D-7D55191555DD--
|
