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
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
|
Return-Path: <jgarzik@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id A6E70BBC
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 3 Jul 2015 03:25:05 +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 6EF22108
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 3 Jul 2015 03:25:04 +0000 (UTC)
Received: by wicgi11 with SMTP id gi11so89072215wic.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 02 Jul 2015 20:25:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type;
bh=mvIuxlLke01IgZT06KpbSchchBHkrUz6lUYuvkwWh7w=;
b=OpigfCO5J0vo/tSaPmf0J3IfHUUzQdQgVJyxW228+eOLuD6H/KH2I5uI7zoU73df9N
F1yZ9II1ZO5ltHiG50AYw4TTLEbcJY4TX5TP0u4xoWZy4BIGnTgaObMzCxBIitfOzhyI
Iv32OgDofzz3ax+Gd3fuxYosBeU0yeu4SbKe23w678tp51G1UPSSbxnYcfW3FAu4/KN+
LZ5Bafp74G3IJrbffu+Wlp5R4aTTeVGJAPosgAYIhfrWRdaTGPbaMq8gRSjmCCrkoscD
AlLVpZStEJdkateNwpq6eJBJytYCDAlQDz6VGRXOM6ZKN/RP8wu4lJNa7BgkAnl7NIRI
8qBQ==
MIME-Version: 1.0
X-Received: by 10.180.79.162 with SMTP id k2mr42536472wix.46.1435893903154;
Thu, 02 Jul 2015 20:25:03 -0700 (PDT)
Received: by 10.28.140.196 with HTTP; Thu, 2 Jul 2015 20:25:03 -0700 (PDT)
In-Reply-To: <CAJ+8mEM-MfRTTTK6-QnrvVtC63N5DZL6PiWSxsqTNm0KSYo=KQ@mail.gmail.com>
References: <F6C7E867-1CCA-4DFB-8A88-361316A76FC3@me.com>
<CABssiCq5JZdkQNmZ1x8OhNYqVxQOPXWe0Ui7wL7dCK9yQe9AoQ@mail.gmail.com>
<5595503D.2010608@phauna.org>
<CAJ+8mEM-MfRTTTK6-QnrvVtC63N5DZL6PiWSxsqTNm0KSYo=KQ@mail.gmail.com>
Date: Thu, 2 Jul 2015 23:25:03 -0400
Message-ID: <CADm_WcbufxsR+MrJ3hkMY60QC9a0v7xKf5VJkK59zxi5pwQxJQ@mail.gmail.com>
From: Jeff Garzik <jgarzik@gmail.com>
To: Jeremy Rubin <jeremy.l.rubin.travel@gmail.com>
Content-Type: multipart/alternative; boundary=f46d043745110865500519f01adc
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,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@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Defining a min spec
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: Fri, 03 Jul 2015 03:25:05 -0000
--f46d043745110865500519f01adc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
If the freedom to pick architecture exists, Moxie is a nice, compact, easy
to audit alternative:
http://moxielogic.org/blog/pages/architecture.html
https://github.com/jgarzik/moxiebox
Scaling can occur at the core level, rather than hyper-pipelining, keeping
the architecture itself nice and clean and simple.
On Thu, Jul 2, 2015 at 11:13 PM, Jeremy Rubin <
jeremy.l.rubin.travel@gmail.com> wrote:
> Might I suggest that the min-spec, if developed, target the RISC-V Rocket
> architecture (running on FPGA, I suppose) as a reference point for
> performance? This may be much lower performance than desirable, however, =
it
> means that we don't lock people into using large-vendor chipsets which ha=
ve
> unknown, or known to be bad, security properties such as Intel AMT.
>
> In general, targeting open hardware seems to me to be more critical than
> performance metrics for the long term health of Bitcoin, however,
> performance is still important.
>
> Does anyone know how the RISC-V FPGA performance stacks up to, say, a
> Raspberry Pi?
>
> On Thu, Jul 2, 2015 at 10:52 PM, Owen Gunden <ogunden@phauna.org> wrote:
>
>> I'm also a user who runs a full node, and I also like this idea. I think
>> Gavin has done some back-of-the-envelope calculations around this stuff,
>> but nothing so clearly defined as what you propose.
>>
>> On 07/02/2015 08:33 AM, Mistr Bigs wrote:
>>
>>> I'm an end user running a full node on an aging laptop.
>>> I think this is a great suggestion! I'd love to know what system
>>> requirements are needed for running Bitcoin Core.
>>>
>>> On Thu, Jul 2, 2015 at 6:04 AM, Jean-Paul Kogelman
>>> <jeanpaulkogelman@me.com <mailto:jeanpaulkogelman@me.com>> wrote:
>>>
>>> I=E2=80=99m a game developer. I write time critical code for a livi=
ng and
>>> have to deal with memory, CPU, GPU and I/O budgets on a daily basis=
.
>>> These budgets are based on what we call a minimum specification (of
>>> hardware); min spec for short. In most cases the min spec is based
>>> on entry model machines that are available during launch, and will
>>> give the user an enjoyable experience when playing our games.
>>> Obviously, we can turn on a number of bells and whistles for people
>>> with faster machines, but that=E2=80=99s not the point of this mail=
.
>>>
>>> The point is, can we define a min spec for Bitcoin Core? The number
>>> one reason for this is: if you know how your changes affect your
>>> available budgets, then the risk of breaking something due to
>>> capacity problems is reduced to practically zero.
>>>
>>>
>>>
>>> _______________________________________________
>>> bitcoin-dev mailing list
>>> bitcoin-dev@lists.linuxfoundation.org
>>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>>
>>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
--f46d043745110865500519f01adc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">If the freedom to pick architecture exists, Moxie is a nic=
e, compact, easy to audit alternative:<div>=C2=A0 =C2=A0 =C2=A0<a href=3D"h=
ttp://moxielogic.org/blog/pages/architecture.html">http://moxielogic.org/bl=
og/pages/architecture.html</a></div><div>=C2=A0 =C2=A0 =C2=A0<a href=3D"htt=
ps://github.com/jgarzik/moxiebox">https://github.com/jgarzik/moxiebox</a></=
div><div><br></div><div>Scaling can occur at the core level, rather than hy=
per-pipelining, keeping the architecture itself nice and clean and simple.<=
/div><div><br></div><div><br></div></div><div class=3D"gmail_extra"><br><di=
v class=3D"gmail_quote">On Thu, Jul 2, 2015 at 11:13 PM, Jeremy Rubin <span=
dir=3D"ltr"><<a href=3D"mailto:jeremy.l.rubin.travel@gmail.com" target=
=3D"_blank">jeremy.l.rubin.travel@gmail.com</a>></span> wrote:<br><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
solid;padding-left:1ex"><div dir=3D"ltr"><span style=3D"font-size:12.80000=
01907349px">Might I suggest that the=C2=A0</span><span style=3D"font-size:1=
2.8000001907349px;background-color:rgb(255,255,255)">min</span><span style=
=3D"font-size:12.8000001907349px">-</span><span style=3D"font-size:12.80000=
01907349px;background-color:rgb(255,255,255)">spec</span><span style=3D"fon=
t-size:12.8000001907349px">, if developed, target the RISC-V Rocket archite=
cture (running on FPGA, I suppose) as a reference point for performance? Th=
is may be much lower performance than desirable, however, it means that we =
don't lock people into using large-vendor chipsets which have unknown, =
or known to be bad, security properties such as Intel AMT.</span><div style=
=3D"font-size:12.8000001907349px"><br></div><div style=3D"font-size:12.8000=
001907349px">In general, targeting open hardware seems to me to be more cri=
tical than performance metrics for the long term health of Bitcoin, however=
, performance is still important.<div><br></div><div>Does anyone know how t=
he RISC-V FPGA performance stacks up to, say, a Raspberry Pi?</div></div></=
div><div class=3D"HOEnZb"><div class=3D"h5"><div class=3D"gmail_extra"><br>=
<div class=3D"gmail_quote">On Thu, Jul 2, 2015 at 10:52 PM, Owen Gunden <sp=
an dir=3D"ltr"><<a href=3D"mailto:ogunden@phauna.org" target=3D"_blank">=
ogunden@phauna.org</a>></span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
I'm also a user who runs a full node, and I also like this idea. I thin=
k Gavin has done some back-of-the-envelope calculations around this stuff, =
but nothing so clearly defined as what you propose.<span><br>
<br>
On 07/02/2015 08:33 AM, Mistr Bigs wrote:<br>
</span><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><span>
I'm an end user running a full node on an aging laptop.<br>
I think this is a great suggestion! I'd love to know what system<br>
requirements are needed for running Bitcoin Core.<br>
<br>
On Thu, Jul 2, 2015 at 6:04 AM, Jean-Paul Kogelman<br></span><span>
<<a href=3D"mailto:jeanpaulkogelman@me.com" target=3D"_blank">jeanpaulko=
gelman@me.com</a> <mailto:<a href=3D"mailto:jeanpaulkogelman@me.com" tar=
get=3D"_blank">jeanpaulkogelman@me.com</a>>> wrote:<br>
<br>
=C2=A0 =C2=A0 I=E2=80=99m a game developer. I write time critical code for =
a living and<br>
=C2=A0 =C2=A0 have to deal with memory, CPU, GPU and I/O budgets on a daily=
basis.<br>
=C2=A0 =C2=A0 These budgets are based on what we call a minimum specificati=
on (of<br>
=C2=A0 =C2=A0 hardware); min spec for short. In most cases the min spec is =
based<br>
=C2=A0 =C2=A0 on entry model machines that are available during launch, and=
will<br>
=C2=A0 =C2=A0 give the user an enjoyable experience when playing our games.=
<br>
=C2=A0 =C2=A0 Obviously, we can turn on a number of bells and whistles for =
people<br>
=C2=A0 =C2=A0 with faster machines, but that=E2=80=99s not the point of thi=
s mail.<br>
<br>
=C2=A0 =C2=A0 The point is, can we define a min spec for Bitcoin Core? The =
number<br>
=C2=A0 =C2=A0 one reason for this is: if you know how your changes affect y=
our<br>
=C2=A0 =C2=A0 available budgets, then the risk of breaking something due to=
<br>
=C2=A0 =C2=A0 capacity problems is reduced to practically zero.<br>
<br>
<br>
<br></span><span>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
<br>
</span></blockquote><div><div>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
<br></blockquote></div><br></div>
--f46d043745110865500519f01adc--
|
