From: Owen Gunden <ogunden@phauna•org>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Defining a min spec
Date: Thu, 02 Jul 2015 10:52:45 -0400 [thread overview]
Message-ID: <5595503D.2010608@phauna.org> (raw)
In-Reply-To: <CABssiCq5JZdkQNmZ1x8OhNYqVxQOPXWe0Ui7wL7dCK9yQe9AoQ@mail.gmail.com>
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’m 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 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’s 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
>
next prev parent reply other threads:[~2015-07-02 14:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 4:04 Jean-Paul Kogelman
2015-07-02 7:18 ` Henning Kopp
2015-07-02 8:33 ` Jean-Paul Kogelman
2015-07-02 12:33 ` Mistr Bigs
2015-07-02 14:52 ` Owen Gunden [this message]
2015-07-03 3:13 ` Jeremy Rubin
2015-07-03 3:25 ` Jeff Garzik
2015-07-03 4:19 ` Jean-Paul Kogelman
2015-07-03 5:33 ` Jeremy Rubin
2015-07-03 6:18 ` Jean-Paul Kogelman
2015-07-03 10:55 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5595503D.2010608@phauna.org \
--to=ogunden@phauna$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox