From: Jameson Lopp <jameson.lopp@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Running a full node
Date: Sat, 08 Nov 2014 16:47:03 -0500 [thread overview]
Message-ID: <545E8F57.5050100@gmail.com> (raw)
In-Reply-To: <CAKaEYhLWv4S0q_kaJNF-AX2nevd+g9MjwO0d02t7iuycj8we7Q@mail.gmail.com>
-----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-----
next prev parent reply other threads:[~2014-11-08 21:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 9:51 Francis GASCHET
2014-11-06 11:09 ` Thomas Zander
2014-11-06 21:38 ` odinn
2014-11-08 15:28 ` Daniel F
2014-11-08 17:44 ` Melvin Carvalho
2014-11-08 21:47 ` Jameson Lopp [this message]
[not found] <545B5323.3000403@numlog.fr>
2014-11-09 15:22 ` Francis GASCHET
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=545E8F57.5050100@gmail.com \
--to=jameson.lopp@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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