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
|
Return-Path: <misterbg6@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 42022BD7
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 2 Jul 2015 12:33:42 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-la0-f49.google.com (mail-la0-f49.google.com
[209.85.215.49])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 57D91ED
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 2 Jul 2015 12:33:41 +0000 (UTC)
Received: by laar3 with SMTP id r3so60163925laa.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 02 Jul 2015 05:33:39 -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:cc
:content-type; bh=Xh2oKqyQgJDO9dDWODehWJBH9Ht0Pm0DftXunG4M3pI=;
b=VZxFEGUWLJcJiIpMMo/N2lJyWfb+58nYk2YRAsIjhWOlIEewJ+yERxJGJBjzRUROzs
nuqNlSTtXSEDItq9j9Hl3TwSQ9ebifj2IdV4JQHudjjMMgEHwtzs0f6iQswfOirUh4Ky
TLBJsS5jK5HoIyXZEQjcFv3txM/aPd06riK11urp53N3ppxE45mIzpSgZJ/ECjmILT1h
HCG8T82XS561xgsLoeiiMgVgYrLq1Jx9dgnyc+V9dTzMJLjWYXksvZT4we7z8JE/z04K
oDrO3KKKfwLqfkG0qaL9MlY9IBQgEZ1HsmK66ehGVmJbkt7AO15B6jvelpwp7QXUZRrM
KRoA==
MIME-Version: 1.0
X-Received: by 10.152.28.194 with SMTP id d2mr30805410lah.122.1435840419724;
Thu, 02 Jul 2015 05:33:39 -0700 (PDT)
Received: by 10.25.2.86 with HTTP; Thu, 2 Jul 2015 05:33:39 -0700 (PDT)
In-Reply-To: <F6C7E867-1CCA-4DFB-8A88-361316A76FC3@me.com>
References: <F6C7E867-1CCA-4DFB-8A88-361316A76FC3@me.com>
Date: Thu, 2 Jul 2015 14:33:39 +0200
Message-ID: <CABssiCq5JZdkQNmZ1x8OhNYqVxQOPXWe0Ui7wL7dCK9yQe9AoQ@mail.gmail.com>
From: Mistr Bigs <misterbg6@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary=089e0160b4202c05380519e3a61d
X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,
HTML_MESSAGE, MISSING_HEADERS,
RCVD_IN_DNSWL_LOW autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.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: Thu, 02 Jul 2015 12:33:42 -0000
--089e0160b4202c05380519e3a61d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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=
>
wrote:
> I=E2=80=99m a game developer. I write time critical code for a living and=
have to
> deal with memory, CPU, GPU and I/O budgets on a daily basis. These budget=
s
> 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 th=
at
> are available during launch, and will give the user an enjoyable experien=
ce
> 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 poin=
t 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.
>
>
--089e0160b4202c05380519e3a61d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>I'm an end user running a full node on an aging l=
aptop.<br></div>I think this is a great suggestion! I'd love to know wh=
at system requirements are needed for running Bitcoin Core.<br><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Jul 2, 2015 at 6:04=
AM, Jean-Paul Kogelman <span dir=3D"ltr"><<a href=3D"mailto:jeanpaulkog=
elman@me.com" target=3D"_blank">jeanpaulkogelman@me.com</a>></span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">
I=E2=80=99m a game developer. I write time critical code for a living and h=
ave to deal with memory, CPU, GPU and I/O budgets on a daily basis. These b=
udgets 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 machine=
s that are available during launch, and will give the user an enjoyable exp=
erience 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 p=
oint of this mail.<br>
<br>
The point is, can we define a min spec for Bitcoin Core? The number one rea=
son 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 t=
o practically zero.<br>
<br></blockquote></div></div></div>
--089e0160b4202c05380519e3a61d--
|
