# Disk fragmentation is inevitable... Do we need to prepare?

**URL:** <https://forum.storj.io/t/disk-fragmentation-is-inevitable-do-we-need-to-prepare/3260>\
**Category:** Node Operators\
**Created:** [December 19, 2019, 1:30am UTC](https://forum.storj.io/t/disk-fragmentation-is-inevitable-do-we-need-to-prepare/3260 "2019-12-19T01:30:22Z")\
**Posts on this page:** 1\
**Showing post:** 31

<div class="post-metadata">

**Author:** ![Toyoo](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/toyoo/32/1126_2.png) [@Toyoo](https://forum.storj.io/u/Toyoo)\
**Post date:** [July 24, 2022, 10:58am UTC](https://forum.storj.io/t/disk-fragmentation-is-inevitable-do-we-need-to-prepare/3260/31 "2022-07-24T10:58:59Z")

</div>

I’ve tested ext4 and btrfs, and of these two ext4 is much faster. And for ext4 [reducing the inode size helps quite a lot](https://forum.storj.io/t/on-tuning-ext4-for-storage-nodes/19073). It also helps to have enough RAM so that inodes stay in cache, I’ve certainly noticed a difference after adding RAM to my NAS.

AFAIK `fast_commit` should not affect the file walker process. What _inode directory optimizations_ do you have in mind?

---

_[View the full topic](https://forum.storj.io/t/disk-fragmentation-is-inevitable-do-we-need-to-prepare/3260)._