From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Xn7wK-00080I-QZ for bitcoin-development@lists.sourceforge.net; Sat, 08 Nov 2014 15:28:36 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.192.54 as permitted sender) client-ip=209.85.192.54; envelope-from=nanotube@gmail.com; helo=mail-qg0-f54.google.com; Received: from mail-qg0-f54.google.com ([209.85.192.54]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Xn7wK-0004jZ-5H for bitcoin-development@lists.sourceforge.net; Sat, 08 Nov 2014 15:28:36 +0000 Received: by mail-qg0-f54.google.com with SMTP id q108so3662322qgd.41 for ; Sat, 08 Nov 2014 07:28:30 -0800 (PST) X-Received: by 10.140.95.106 with SMTP id h97mr25724097qge.97.1415460510766; Sat, 08 Nov 2014 07:28:30 -0800 (PST) Received: from [192.168.2.102] (c-76-117-112-138.hsd1.nj.comcast.net. [76.117.112.138]) by mx.google.com with ESMTPSA id 45sm8580312qgg.37.2014.11.08.07.28.30 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 08 Nov 2014 07:28:30 -0800 (PST) Message-ID: <545E3690.2060908@gmail.com> Date: Sat, 08 Nov 2014 10:28:16 -0500 From: Daniel F User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net, fg@numlog.fr References: <545B44AA.7030107@numlog.fr> In-Reply-To: <545B44AA.7030107@numlog.fr> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (nanotube[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Xn7wK-0004jZ-5H Subject: Re: [Bitcoin-development] Running a full node X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Nov 2014 15:28:37 -0000 > But I'd like to know what storage, RAM and bandwidth resources are > needed. I guess that the problem is not the CPU. Hi Francis, Here are some rough guidelines for you, based on the statistics from my node: disk usage: about 30GB currently for the blockchain data. It'll only keep growing from here, but relatively slowly. cpu usage: pretty much nothing, after you have synced the blockchain. ram usage: after it runs for a few months, my node gets up to using 1.5 GB of ram or so. bandwidth usage: my node averages about 500GB of traffic per month, most of it outgoing. Hope that gives you a rough idea of what you can expect for running full node. Best, Daniel