Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <jameson.lopp@gmail.com>) id 1XnDqi-0002OU-37 for bitcoin-development@lists.sourceforge.net; Sat, 08 Nov 2014 21:47:12 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.192.48 as permitted sender) client-ip=209.85.192.48; envelope-from=jameson.lopp@gmail.com; helo=mail-qg0-f48.google.com; Received: from mail-qg0-f48.google.com ([209.85.192.48]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XnDqg-0007NR-KH for bitcoin-development@lists.sourceforge.net; Sat, 08 Nov 2014 21:47:12 +0000 Received: by mail-qg0-f48.google.com with SMTP id q108so3910707qgd.7 for <bitcoin-development@lists.sourceforge.net>; Sat, 08 Nov 2014 13:47:05 -0800 (PST) X-Received: by 10.224.38.130 with SMTP id b2mr30528172qae.11.1415483225162; Sat, 08 Nov 2014 13:47:05 -0800 (PST) Received: from [192.168.0.13] (cpe-098-026-000-034.nc.res.rr.com. [98.26.0.34]) by mx.google.com with ESMTPSA id m16sm11691649qaf.11.2014.11.08.13.47.04 for <bitcoin-development@lists.sourceforge.net> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 08 Nov 2014 13:47:04 -0800 (PST) Message-ID: <545E8F57.5050100@gmail.com> Date: Sat, 08 Nov 2014 16:47:03 -0500 From: Jameson Lopp <jameson.lopp@gmail.com> 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 References: <545B44AA.7030107@numlog.fr> <545E3690.2060908@gmail.com> <CAKaEYhLWv4S0q_kaJNF-AX2nevd+g9MjwO0d02t7iuycj8we7Q@mail.gmail.com> In-Reply-To: <CAKaEYhLWv4S0q_kaJNF-AX2nevd+g9MjwO0d02t7iuycj8we7Q@mail.gmail.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit 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 (jameson.lopp[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: 1XnDqg-0007NR-KH 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: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Sat, 08 Nov 2014 21:47:12 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I host charts of my node's system metrics at http://statoshi.info/#/dashboard/db/system-metrics Note that the CPU spikes are abnormal as I'm making automated RPC calls to query the UTXO set. My node's bandwidth usage chart can be found at http://statoshi.info/#/dashboard/file/default.json?panelId=1&fullscreen - - Jameson On 11/08/2014 12:44 PM, Melvin Carvalho wrote: > On 8 November 2014 16:28, Daniel F <nanotube@gmail.com> wrote: > >>> 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. >> > > There's some statistics on this site: > > https://blockchain.info/charts/blocks-size > > It may be reasonable to assume 10GB growth a year. When I was running a > full node I gave it a disk of 50GB. > > >> >> 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 >> >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Bitcoin-development mailing list >> Bitcoin-development@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/bitcoin-development >> > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUXo9XAAoJEIch3FSFNiDcl20H/0/MrFt0SfR5G5S0m4sLMUdP 5/sveDnVjCBBmcoCKvH3XKchT7fVA6C4N1+dUYDJhlOaZhXegdY3saHdIP/sFzkF 38JBdoqWm4IysAC9gmtn/jRSrxh0wC780zVcLe2EgI7n+1ZOOqCaud28gX+ukoq5 dsU/B8bPEZ/2E7WbaXRcJJGqPdP03H2VXEkKxTWacBYFGVd6RhP9ieFHS3TyctNb A0g02l1OmymnSSP6ze32ne+G4RgPdbvYhevW8vay1P4ATgBSnB2sitawRXJjsxMy +d4Fqg+xYRMx3l8lamb7OLSi9rMe6GNEKyML4/Gu24JPSjlmQLXRJE/aS3oMyZc= =zXHK -----END PGP SIGNATURE-----