From: Peter Todd <pete@petertodd•org>
To: "Juan David Peña Melo" <jdom1824@gmail•com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] How was the average size of blk*.data chosen?
Date: Thu, 30 May 2024 18:20:57 +0000 [thread overview]
Message-ID: <ZljDiesLp29yqipn@petertodd.org> (raw)
In-Reply-To: <af58fdac-f62f-44b6-8c30-37bb8ad8c4e3n@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]
On Mon, May 06, 2024 at 06:23:47PM -0700, Juan David Peña Melo wrote:
> I notice that the Bitcoin database is stored sequentially in blk*.dat
> files, with an average size between 128 to 134MB. I would like to know how
> this average size is determined and if there are any tests that demonstrate
> this size is the most efficient.
Most likely someone just picked a number at random. For things like this, there
is a very wide range of values that are probably fine. The main limiting factor
at the high end, is some older file systems still don't support files >4GB, so
you'd want to pick a value below that; Monero all block data in a single file,
and that occasionally leads to issues when, eg, copying that file from one
place to another. At the low end, having tens of thousands of files in one
directory tends to cause problems.
--
https://petertodd.org 'peter'[:-1]@petertodd.org
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups•com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoindev/ZljDiesLp29yqipn%40petertodd.org.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-05-30 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 1:23 Juan David Peña Melo
2024-05-30 18:20 ` Peter Todd [this message]
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=ZljDiesLp29yqipn@petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=bitcoindev@googlegroups.com \
--cc=jdom1824@gmail$(echo .)com \
/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