MIME-Version: 1.0
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
Subject: Re: [bitcoin-dev] Defining a min spec
Precedence: list

--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&#39;m an end user running a full node on an aging l=
aptop.<br></div>I think this is a great suggestion! I&#39;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">&lt;<a href=3D"mailto:jeanpaulkog=
elman@me.com" target=3D"_blank">jeanpaulkogelman@me.com</a>&gt;</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--