public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mistr Bigs <misterbg6@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Defining a min spec
Date: Thu, 2 Jul 2015 14:33:39 +0200	[thread overview]
Message-ID: <CABssiCq5JZdkQNmZ1x8OhNYqVxQOPXWe0Ui7wL7dCK9yQe9AoQ@mail.gmail.com> (raw)
In-Reply-To: <F6C7E867-1CCA-4DFB-8A88-361316A76FC3@me.com>

[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]

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’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.
>
>

[-- Attachment #2: Type: text/html, Size: 1376 bytes --]

  parent reply	other threads:[~2015-07-02 12:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-02  4:04 [bitcoin-dev] Defining a min spec 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 [this message]
2015-07-02 14:52   ` Owen Gunden
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=CABssiCq5JZdkQNmZ1x8OhNYqVxQOPXWe0Ui7wL7dCK9yQe9AoQ@mail.gmail.com \
    --to=misterbg6@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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