From: "Juan David Peña Melo" <jdom1824@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] How was the average size of blk*.data chosen?
Date: Mon, 6 May 2024 18:23:47 -0700 (PDT) [thread overview]
Message-ID: <af58fdac-f62f-44b6-8c30-37bb8ad8c4e3n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 646 bytes --]
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.
--
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/af58fdac-f62f-44b6-8c30-37bb8ad8c4e3n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1043 bytes --]
next reply other threads:[~2024-05-07 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 1:23 Juan David Peña Melo [this message]
2024-05-30 18:20 ` [bitcoindev] How was the average size of blk*.data chosen? Peter Todd
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=af58fdac-f62f-44b6-8c30-37bb8ad8c4e3n@googlegroups.com \
--to=jdom1824@gmail.com \
--cc=bitcoindev@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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