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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gronager@mac.com>) id 1StaQl-0006Gq-6k
for bitcoin-development@lists.sourceforge.net;
Tue, 24 Jul 2012 08:25:23 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of mac.com
designates 17.172.81.1 as permitted sender)
client-ip=17.172.81.1; envelope-from=gronager@mac.com;
helo=st11p00mm-asmtpout002.mac.com;
Received: from st11p00mm-asmtpout002.mac.com ([17.172.81.1])
by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1StaQf-0003Tg-LI for bitcoin-development@lists.sourceforge.net;
Tue, 24 Jul 2012 08:25:23 +0000
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Received: from [109.105.106.237] (unknown [109.105.106.237])
by st11p00mm-asmtp002.mac.com
(Oracle Communications Messaging Exchange Server 7u4-22.01 64bit (built
Apr 21
2011)) with ESMTPSA id <0M7N006T1OPXA580@st11p00mm-asmtp002.mac.com>
for bitcoin-development@lists.sourceforge.net; Tue,
24 Jul 2012 08:25:12 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure
engine=2.50.10432:5.7.7855,1.0.260,0.0.0000
definitions=2012-07-24_02:2012-07-24, 2012-07-24,
1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0
ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0
classifier=spam
adjust=0 reason=mlx scancount=1 engine=6.0.2-1203120001
definitions=main-1207240017
From: =?iso-8859-1?Q?Michael_Gr=F8nager?= <gronager@mac.com>
In-reply-to: <500D73B9.5030806@mistfpga.net>
Date: Tue, 24 Jul 2012 10:25:09 +0200
Content-transfer-encoding: quoted-printable
Message-id: <B872EE35-36F9-4F4E-8342-FFA141E433C7@mac.com>
References: <CAD2Ti29dqCYoOMcX0zcOQnpLGCxnCjYHHqMzyyq+hvcVQ2c7nQ@mail.gmail.com>
<CAAS2fgTHrWdXHbX8oiLgnrhdC+yxL4QyPd7S4iB8RMNip_sUGg@mail.gmail.com>
<A428177D-62AD-4712-9053-47B7ED5DBC84@mac.com>
<500D73B9.5030806@mistfpga.net>
To: steve <steve@mistfpga.net>
X-Mailer: Apple Mail (2.1278)
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
(gronager[at]mac.com)
-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 MALFORMED_FREEMAIL Bad headers on message from free email service
X-Headers-End: 1StaQf-0003Tg-LI
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Scalability issues
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: Tue, 24 Jul 2012 08:25:23 -0000
Hi Steve,
45-90 minutes - note that its numbers from March/April, so a bit longer =
today, but far, far away from the 12 hours.=20
I am using libcoin and the bitcoind build based on this. Libcoin is =
based on the Satoshi client, but refactured to use an async concurrency =
model. I also did a minor tweeks to the db parameters. It has earlier =
been tested up against Satoshi bitcoin where on some OS'es it performs =
similarly (at least on some linuxes) and on some faster (e.g. mac).=20
What is your CPU load during a block download ? (both initially/up to =
the point where verification sets in and after). The initial download is =
typically disk I/O bound, the verification stage CPU bound, though I =
lean to believe that even there it is disk I/O bound (at least on my =
system ~50% CPU load). What should be better in libcoin is the =
concurrency model. The Satoshi client uses a pure reentrant mutexes =
model, that is not generally believed to motivate the best coding =
practice nor performance, you might end up without the concurrency you =
initially strived for *). As mentioned earlier libcoin uses a pure async =
concurrency model (and so does libbitcoin btw).=20
I would like to stress again that these numbers will depend largely on =
the system running the test - I would call my laptop a bit over the =
average today (MB Pro, 2.66Ghz i7 dual core, 8GBRAM, 512GB SSD). But =
again 12 hours - I only reach such numbers on some of my VPS'es (linode =
1024) that are known for notoriously slow disk I/O. (here I have a few % =
CPU load during the verification indicating indeed that the disk i/o is =
the culprit).
Cheers,
Michael
*) I like this Dave Butenhof quote: "The biggest of all the big problems =
with recursive mutexes is that they encourage you to completely lose =
track of your locking scheme and scope. This is deadly. Evil. It's the =
"thread eater". You hold locks for the absolutely shortest possible =
time. Period. Always. If you're calling something with a lock held =
simply because you don't know it's held, or because you don't know =
whether the callee needs the mutex, then you're holding it too long. =
You're aiming a shotgun at your application and pulling the trigger. You =
presumably started using threads to get concurrency; but you've just =
PREVENTED concurrency."
On 23/07/2012, at 17:54, steve wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> Hi Michael,
>=20
> On 23/07/2012 10:00, Michael Gr=F8nager wrote:
>> I get a full blockchain from scratch in 45 minutes on my laptop,
>> /M
>>=20
> Hang on a sec, in 45 minutes you can download the entire chain from
> the genesis block?
>=20
> I have been doing extensive testing in this area and would love to
> know what is special about your setup (I have never had the entire
> chain in under 12 hours, infact it is normally closerto 24.) I have an
> extensive setup of test machines, everything from e4300 to phenom2x6
> to i5's.
>=20
> as an example on an amd e-450 with 4gb ram, and approx 3gb/s internet
> connection it took 2 hours to sync the last 5 days.
>=20
> Maybe i am missing something important...
>=20
> Any additional information that you could provide to help me with
> testing would be really appreciated.
>=20
> cheers,
>=20
> steve
>=20
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.17 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>=20
> iQEcBAEBAgAGBQJQDXO4AAoJEFvEB9dQFvtQxdcH/ieqQkyDCg8mKeOa6CqsWaS6
> fhoeny3Ke2b/CsvhYmsThCvntN9volIqR2CTn5tkHiVwG9OmlxyHZcNpN0ZTHhK5
> lsfLap/Y0QpiysXpV4Bu7Z4Hwp9jnhOP74TshT305r2pX6EGXPQ0CrlHqlIry/X/
> vNcunUclliou+KjL7EHcY50GH5wDpqJAjlNyF97Lj9YiPrAC9vahGwWdxkbCYtG+
> KUuWGBKMMdHuMAgcQh7nI9q0WT3k/gzRQtuC2kf+v0wvQhaGlTVkku4uanhpuw4p
> 99blRF3/SfWimGuQgsm6wT3Y7dk+z8MFHLb6XGPxmgV9+gF+TWNczfU3GRzfcXw=3D
> =3DCQkI
> -----END PGP SIGNATURE-----
>=20
> =
--------------------------------------------------------------------------=
----
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and=20
> threat landscape has changed and how IT managers can respond. =
Discussions=20
> will include endpoint security, mobile security and the latest in =
malware=20
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
|
