<p>Blocks are stored in large contiguous files (gigabytes), and are effectively append only, so they don’t really make any sort of impact on performance. </p>

<p>The high write cycle is in a several gigabyte leveldb database, but this is heavily write cached. Performance is almost always single core limited on any sort of fast storage given sufficient memory, rather than any other other factor. </p>

<p>You’ll only see storage as a factor when using magnetic media or excruciatingly slow flash storage like a SD card. </p>

CC BY-SA 4.0
2020-04-19T07:29:11.147Z
2020-04-19T16:12:34.220Z
2020-04-19T16:12:34.220Z
Claris
<p>I'm formatting a SSD for a new node and searched here that Gavin said the typical blockchain file size was 250kb (2015), others showed 500kb (2018). I thought is was to remain constant, so perhaps one answer is wrong, then again it may be 999kb soon.  When formatting you can choose your AUS if you relatively know your file size to pack it more efficiently. </p>

<p>The first two AUS choices are 512kb and 1024kb. I think much better choices than the default 32,768kb. Am I missing something here or am I going to achieve a rough 4-5x benefit here? Thx</p>

CC BY-SA 4.0
2020-04-19T07:30:13.233Z
Many blocks today exceed 1.5MB, even so far as 2.2MB recently.
Claris
<full-node>
Allocation Unit Size (AUS) when formatting drive
wmnstack
# Allocation Unit Size (AUS) when formatting drive

(Asked by: username_0 on 2020-04-19)

I'm formatting a SSD for a new node and searched here that Gavin said the typical blockchain file size was 250kb (2015), others showed 500kb (2018). I thought is was to remain constant, so perhaps one answer is wrong, then again it may be 999kb soon. When formatting you can choose your AUS if you relatively know your file size to pack it more efficiently.

The first two AUS choices are 512kb and 1024kb. I think much better choices than the default 32,768kb. Am I missing something here or am I going to achieve a rough 4-5x benefit here? Thx

**Tags:** full-node

> **Comments:**
> **username_1**: Many blocks today exceed 1.5MB, even so far as 2.2MB recently.  

---

## 1 answers

### Answer by username_1 on 2020-04-19. Score: 1 | Accepted answer

Blocks are stored in large contiguous files (gigabytes), and are effectively append only, so they don’t really make any sort of impact on performance.

The high write cycle is in a several gigabyte leveldb database, but this is heavily write cached. Performance is almost always single core limited on any sort of fast storage given sufficient memory, rather than any other other factor.

You’ll only see storage as a factor when using magnetic media or excruciatingly slow flash storage like a SD card.


---

