I never really pay block size much attention but obviously there can be benefits to choosing something other than the default. I am looking for a good "best practices" paper on choosing block size. Also, when used on top of LVM is it's performance payoffs or importance negated in any way? TIA
Best Practices for Choosing FS Block Size on ext3/ext4
ext3filesystemsperformance
Related Topic
- Linux – MySQL InnoDB ext3 block size
- Linux – Choosing file system block size
- CentOS RAID 5 – Configuring RAID 5 with 24 x 1.2 TB Drives
- Sizing of journal disks with Microsoft Storage Spaces parity volume
- Linux – iostat – dm-0 device shows much higher latencies than sdX
- Using correct number of DIMMS for best memory performance Intel Xeon scalable cpu
Best Answer
Short answer:
4096
Longer answer:
Larger block sizes reduce fragmentation, at the cost of some wasted space at the end of the block. Having said that, give the size of most hard drives these days, unless you are storing something like a mail or news spool you should use
4096
as it matches the page size (in memory) with the block size on disk.If you are storing a mail spool, then you should look at using something like XFS which is more efficient at storing large numbers of small files.