Ninjastic
PostEdited versionsQuotes to this post
Next scheduled rescrape ... never
Version 1
Last scraped
Scraped on 22/09/2025, 21:53:27 UTC
Quote from: Findingnemo on August 15, 2025, 08:43:49 PM
Even 8GB is not that much atleast 16 GB will give more space for core to stress the system and if someone wants to download full node then it must be around 650GB so make sure you have atleast 700GB for running your full node and NVMe is recommended since R/W will be faster and it's more reliable.
On OPs VPS Bitcoin Core seems to run fine with 4GiB RAM. I never had issues running Bitcoin Core on my Raspis which have 8GiB RAM, but more is better, especially to speed up initial blockchain download for which you want to raise dbcache value preferably to around 12 GiB. But if you're patient it works fine with less. Not to mention if you want to run an Electrum server on the same device.

For a non-pruned, full archival node you need more space. Here's what one of my nodes consume as of right now (I've txindex=1 and the blockfilter stuff enabled):
Code:
11G ./chainstate
61G ./indexes/txindex
105M ./indexes/blockfilter/basic/db
12G ./indexes/blockfilter/basic
12G ./indexes/blockfilter
72G ./indexes
138M ./blocks/index
731G ./blocks
813G .
Original archived Re: Running My First Bitcoin Node – My Experience & Setup Guide
Scraped on 22/09/2025, 21:48:05 UTC
Quote from: Findingnemo on August 15, 2025, 08:43:49 PM
Even 8GB is not that much atleast 16 GB will give more space for core to stress the system and if someone wants to download full node then it must be around 650GB so make sure you have atleast 700GB for running your full node and NVMe is recommended since R/W will be faster and it's more reliable.
On OPs VPS Bitcoin Core seems to run fine with 4GiB RAM. I never had issues running Bitcoin Core on my Raspis which have 8GiB RAM, but more is better, especially to speed up initial blockchain download for which you want to raise dbcache value preferably to around 12 GiB. But if you're patient it works fine with less.

For a non-pruned, full archival node you need more space. Here's what one of my nodes consume as of right now (I've txindex=1 and the blockfilter stuff enabled:
Code:
11G ./chainstate
61G ./indexes/txindex
105M ./indexes/blockfilter/basic/db
12G ./indexes/blockfilter/basic
12G ./indexes/blockfilter
72G ./indexes
138M ./blocks/index
731G ./blocks
813G .