Difference between revisions of "Performance tuning"

Jump to navigation Jump to search
279 bytes added ,  21:31, 27 June 2020
m
Added more information on incompressible data under LZ4 compression
m (Added more information on incompressible data under LZ4 compression)
Line 126: Line 126:
=== LZ4 compression ===
=== LZ4 compression ===


Set compression=lz4 on your pools' root datasets so that all datasets inherit it unless you have a reason not to enable it. Userland tests of LZ4 compression of incompressible data in a single thread has shown that it can process 10GB/sec, so it is unlikely to be a bottleneck even on incompressible data. The reduction in IO from LZ4 will typically be a performance win.
Set compression=lz4 on your pools' root datasets so that all datasets inherit it unless you have a reason not to enable it. Userland tests of LZ4 compression of incompressible data in a single thread has shown that it can process 10GB/sec, so it is unlikely to be a bottleneck even on incompressible data. Furthermore, incompressible data will be stored without compression such that reads of incompressible data with compression enabled will not be subject to decompression. Writes are so fast that in-compressible data is unlikely to see a performance penalty from the use of LZ4 compression. The reduction in IO from LZ4 will typically be a performance win.  


Note that compression ratios will see minor increases from larger recordsize settings because more data may be considered by the compression algorithm at a time.
Note that larger record sizes will increase compression ratios on compressible data by allowing compression algorithms to process more data at a time.


=== NVMe low level formatting ===
=== NVMe low level formatting ===
Editor
348

edits

Navigation menu