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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@exmulti.com>) id 1TR8vM-0008M7-Rz
for bitcoin-development@lists.sourceforge.net;
Wed, 24 Oct 2012 21:55:40 +0000
X-ACL-Warn:
Received: from mail-qa0-f54.google.com ([209.85.216.54])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1TR8vL-00082E-UB
for bitcoin-development@lists.sourceforge.net;
Wed, 24 Oct 2012 21:55:40 +0000
Received: by mail-qa0-f54.google.com with SMTP id p27so1750858qat.13
for <bitcoin-development@lists.sourceforge.net>;
Wed, 24 Oct 2012 14:55:34 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=mime-version:x-originating-ip:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type:x-gm-message-state;
bh=OQTG5wq70IqEFi93oEU6SGkihlx3sBTIRHquf/+QIlM=;
b=kuuG8mSnO9n5Lc4YlSNhv3EuHs/8qLpx09hHSs6yA01CbcxB89LEQJ8T5bHHar50MF
aP/o2UjrppQi4ZC/fj2kzUtwAv33FIillAVD/DXnNRzJOhGjGTns59h2siqS7RJDoWdL
tGyTMqZ3PLptafUXEyWwnZ/hJ44NZ1YwPwb8CRe94/5NiLwTNNkJDjzWylOVreU5L4Wb
YU3eAchCufwj/+8v6JFxz8wwcaVWQiBzYbaY9dJfs5jZGfgJAPn9PJ+oVpd7odHznhdW
hxl474ObfomHK37ddRYHILVFkJzpRVYAZw1uUe1P+wKz4E+jONxG/ODMT4r61yNrjUuR
WeUg==
MIME-Version: 1.0
Received: by 10.229.137.70 with SMTP id v6mr2009056qct.69.1351115734287; Wed,
24 Oct 2012 14:55:34 -0700 (PDT)
Received: by 10.49.97.6 with HTTP; Wed, 24 Oct 2012 14:55:34 -0700 (PDT)
X-Originating-IP: [2001:4830:1603:2:21c:c0ff:fe79:c8c2]
In-Reply-To: <CABsx9T2Oc+LeJjczG_U9u06gkQRmSP0J8Q_hEJv0oGQLnKFuJw@mail.gmail.com>
References: <CANEZrP0XALwBFJyZTzYd5xBp4MRrjv0s_y2tOXbO7UgjWF2HzA@mail.gmail.com>
<20121024162255.GA30290@vps7135.xlshosting.net>
<CANEZrP1sxtOb+czMtBTkmzngEwMYRqD667WyKQkAOKLi+mGBGQ@mail.gmail.com>
<20121024171104.GA31766@vps7135.xlshosting.net>
<CABsx9T0JyFJKLWK09NEzDk6B9Z2Yz7T55kf8GJ2o3ViCnBpRAw@mail.gmail.com>
<CANEZrP1AFL6ZbV7Njr1s8ggsZkQA1dv_3LYT3z+y83UKqn7Kgg@mail.gmail.com>
<CABsx9T2Oc+LeJjczG_U9u06gkQRmSP0J8Q_hEJv0oGQLnKFuJw@mail.gmail.com>
Date: Wed, 24 Oct 2012 17:55:34 -0400
Message-ID: <CA+8xBpfNCbAEtotORbY-iR+KRCE4oN_PT0ZmTekhiYi3Uh2+Ag@mail.gmail.com>
From: Jeff Garzik <jgarzik@exmulti.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQk603ozaTnjgIW9BfpO+4FkNurtGlJDVaJUDE9E+jTkBON/Cb/QKiSlP9cwzL3zehlpe319
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1TR8vL-00082E-UB
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Draft BIP for Bloom filtering
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 21:55:41 -0000
On Wed, Oct 24, 2012 at 4:29 PM, Gavin Andresen <gavinandresen@gmail.com> wrote:
> Oops, right. That memory usage is bounded right now by bounds on the
> memory pool size, though, right? (I'm being lazy and not digging into
> that code)
Correct me if I'm wrong but... I do not think there is any bound on
mempool size.
My proposal to age-out long-unconfirmed transactions is related, but
does not completely solve the unbounded-size issue.
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com
|
