# Best Record size for zfs

**URL:** <https://forum.storj.io/t/best-record-size-for-zfs/10871>\
**Category:** getting started\
**Tags:** zfs\
**Created:** [December 25, 2020, 11:56am UTC](https://forum.storj.io/t/best-record-size-for-zfs/10871 "2020-12-25T11:56:34Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![kevink](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/kevink/32/6077_2.png) [@kevink](https://forum.storj.io/u/kevink)\
**Post date:** [December 25, 2020, 10:15pm UTC](https://forum.storj.io/t/best-record-size-for-zfs/10871/7 "2020-12-25T22:15:53Z")

</div>

lz4 is pretty fast so the latency is not relevant actually but you could even switch to lze. The only reason to use compression is to shorten the records. E.g. if you have a 2.3MB file and 1MB recordsize then you’d need 3 records to store that file. Then you have 3MB of used space, even though that file is only 2.3MB. With compression that last record would be shortened to 0.3MB. That’s why I have a compressratio of 1.3 on my latest node dataset with 512K recordsize.  
Apart from that you are right, you shouldn’t be able save any real space because the data is encrypted.

---

_[View the full topic](https://forum.storj.io/t/best-record-size-for-zfs/10871)._