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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <imichaelmiers@gmail.com>) id 1TJSuA-0004bV-FO
for bitcoin-development@lists.sourceforge.net;
Wed, 03 Oct 2012 17:38:42 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.216.175 as permitted sender)
client-ip=209.85.216.175; envelope-from=imichaelmiers@gmail.com;
helo=mail-qc0-f175.google.com;
Received: from mail-qc0-f175.google.com ([209.85.216.175])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1TJSu6-0000V4-Tw
for bitcoin-development@lists.sourceforge.net;
Wed, 03 Oct 2012 17:38:42 +0000
Received: by qcsj3 with SMTP id j3so3726903qcs.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 03 Oct 2012 10:38:33 -0700 (PDT)
Received: by 10.224.180.132 with SMTP id bu4mr8326397qab.62.1349285913413;
Wed, 03 Oct 2012 10:38:33 -0700 (PDT)
MIME-Version: 1.0
Sender: imichaelmiers@gmail.com
Received: by 10.49.30.40 with HTTP; Wed, 3 Oct 2012 10:38:13 -0700 (PDT)
In-Reply-To: <CAEC9zAYrMHHEyyTx1QVHoGSJU3fFypB0Hx4K-VFoUn0hp4Z7JA@mail.gmail.com>
References: <CAEC9zAbHO9y7Go4FhZFyOCKdm1js_eKCoz7iaOCh1Wu=B9OASw@mail.gmail.com>
<CAEC9zAYrMHHEyyTx1QVHoGSJU3fFypB0Hx4K-VFoUn0hp4Z7JA@mail.gmail.com>
From: Ian Miers <imiers1@jhu.edu>
Date: Wed, 3 Oct 2012 13:38:13 -0400
X-Google-Sender-Auth: o9JOzvmtUDuLSXtb6avhFUS_OVk
Message-ID: <CAEC9zAbkWWcn5eRHLh6u+zyGu92E1Yq-9CQVPqE_6-QwMVs=4Q@mail.gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=20cf303b42f791ca2004cb2b1b49
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(imichaelmiers[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1TJSu6-0000V4-Tw
Subject: Re: [Bitcoin-development] performance testing for bitcoin
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, 03 Oct 2012 17:38:42 -0000
--20cf303b42f791ca2004cb2b1b49
Content-Type: text/plain; charset=ISO-8859-1
Whats the best way to get performance numbers for modifications to bitcoin
? Profiling it while running on testnet might work, but that would take a
rather long time to get data.
Is there anyway to speed this up if we only needed to
provide relative performance between tests. (in a sense a fast performance
regression test).
At least in theory, one possibility would be to replay real
bitcoin transactions to a test-net-in-a-box network (of maybe a few nodes)
that has the real blockchain history loaded into it but then operates at a
far reduced hash difficulty in order facilitate running quickly.
Are there existing techniques/scripts for some kind of perf testing with
traffic that at least approximates real world traffic ?
The test infrastructure that ships with bitcoin does not appear to provide
this.
Thanks,
Ian
>
>
--20cf303b42f791ca2004cb2b1b49
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div class=3D"gmail_quote">Whats the best way to get performance numbers fo=
r modifications to bitcoin ? Profiling it while running on testnet might wo=
rk, but that would take a rather long time to get data.=A0<br>Is there anyw=
ay to speed this up =A0if we only needed to provide=A0=A0relative=A0perform=
ance=A0between tests.=A0(in a sense a fast performance regression test).<br=
>
<br>At least in theory, one possibility would be to replay real bitcoin=A0t=
ransactions=A0 to a test-net-in-a-box network (of maybe a few nodes)<br>tha=
t has the real=A0blockchain=A0history loaded into it but then operates at a=
far reduced hash difficulty in order facilitate running quickly.<br>
<br>Are there existing techniques/scripts for =A0some kind of perf testing =
with traffic that at least approximates real world traffic ?=A0<br>The test=
=A0infrastructure=A0=A0that ships with bitcoin does not appear to provide t=
his.<br>
<br>Thanks,<br>Ian<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"HOEnZb">=
<div class=3D"h5"><br>
</div></div></blockquote></div><br>
--20cf303b42f791ca2004cb2b1b49--
|
