meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
linux:fs:zfs:tuning [2025/01/04 16:18] – niziaklinux:fs:zfs:tuning [2026/03/20 07:51] (current) – niziak
Line 1: Line 1:
 ====== ZFS performance tuning tips ====== ====== ZFS performance tuning tips ======
  
-===== Tune L2ARC for backups =====+Copy-paste snippet: 
 +<code bash> 
 +zfs set recordsize=1M rpool 
 +zfs set recordsize=16M hddpool 
 +zfs set recordsize=1M nvmpool 
 +zfs set compression=zstd rpool 
 +zfs set compression=zstd hddpool 
 +zfs set compression=zstd nvmpool 
 +</code>
  
-When huge portion of data are written (new backups) or read (backup verify) L2ARC is constantly written with current data. +**Note:** ''zstd'' means ''zstd-3''. It is still CPU hungry compression, and it is visible on ''top'' monitoring. For high workloads like build nodes use ''lz4'' 
-To change this behaviour to cache only ''Most Frequent Use'':+See more in [[linux:fs:zfs:compression]]
  
-<file conf /etc/modprobe.d/zfs.conf> + 
-options zfs l2arc_mfuonly=1 l2arc_noprefetch=0+===== zil limit ===== 
 + 
 +ZFS parameter [[https://openzfs.github.io/openzfs-docs/Performance%20and%20Tuning/Module%20Parameters.html#zil-slog-bulk|zil_slog_bulk]] is responsible to ''throttle'' LOG device load. In older ZFS valu was set to 768kB, currently it is 64MB. All sync write requests above this size will be treated as async requests and written directly to slower main device. 
 + 
 +<file ini /etc/modprobe.d/zfs.conf> 
 +options zfs zil_slog_bulk=67108864 
 +options zfs l2arc_write_max=67108864
 </file> </file>
  
-Explanation: +See similar for L2ARC: [[https://openzfs.github.io/openzfs-docs/Performance%20and%20Tuning/Module%20Parameters.html#l2arc-write-max|l2arc_write_max]]
-  * [[https://openzfs.github.io/openzfs-docs/Performance%20and%20Tuning/Module%20Parameters.html#l2arc-mfuonly|l2arc_mfuonly]] Controls whether only MFU metadata and data are cached from ARC into L2ARC. This may be desirable to avoid wasting space on L2ARC when reading/writing large amounts of data that are not expected to be accessed more than once. By default both MRU and MFU data and metadata are cached in the L2ARC. +
-  * [[https://openzfs.github.io/openzfs-docs/Performance%20and%20Tuning/Module%20Parameters.html#l2arc-noprefetch|l2arc_noprefetch]] Disables writing prefetched, but unused, buffers to cache devices. Setting to 0 can increase L2ARC hit rates for workloads where the ARC is too small for a read workload that benefits from prefetching. Also, if the main pool devices are **very slow**, setting to 0 can improve some workloads such as **backups**.+
  
-===== I/O scheduler =====+===== recordsize / volblocksize =====
  
 +Size must be power of 2.
  
-If whole device is managed by ZFS (not partition), ZFS sets scheduler to ''none''. +  * ZFS file system: ''recordsize''  (default 128kB) 
 +  * ZVOL block device: ''volblocksize''  (default - Solaris based - was 8kB). With OpenZFS 2.2 default was changed to 16k to "reduce wasted space".
  
-==== official recommendation ====+This is basic operation unit for ZFS. ZFS is COW filesystem. So to modify even one byte of data stored inside 128kB record it must read 128kB record, modify it and store 128kB in new place. It creates huge read and write amplification.
  
-For rotational devices, there is no sense to use advanced schedulers ''cfq'' or ''bfq'' directly on hard disc. +Small sizes:
-Both depends on processes, processes groups and application. In this case there is group of kernel processess for ZFS.+
  
-Only possible scheduler to consider is ''deadline'' / ''mq-deadline''.  +  * are good for dedicated workloads, like databases, etc. 
-''Deadline'' scheduler group reads into batches and writed into separate batches ordering by increasing LBA address (so it should be good for HDDs).+  * 4kB has no sense with compression. Even if data is compressed below 4kB it still occupies smallest possible unit - 4kB. 
 +  * slower sequential read - lots of IOPS and checksum checks 
 +  * fragmentation over time 
 +  * metadata overhead (4kB data size needs also metada, so another 4kB unit will be used).
  
-There is a discussion on OpenZFS project to do not touch schedulers anymore and let it to be configured by admin: +Big size:
-  * [[https://github.com/openzfs/zfs/pull/9042|Set "none" scheduler if available (initramfs) #9042]] +
-  * [[https://github.com/openzfs/zfs/commit/42c24d90d112b6e9e1a304346a1335e058f1678b]]+
  
-==== my findings ====+  * benefit from compression. I.e: 128kB data compressed to 16kB will create 16kB record size. 
 +  * very good for storage (write once data) 
 +  * read/write amplification for small read/writes 
 +  * good for sequential access 
 +  * good for HDDs (less fragmentation = less seeks) 
 +  * less metadata 
 +  * less fragmentation 
 +  * zvol: huge overhead if guest is using small block sizes - try to match guest FS block size to volblock - do not set 4kB volblock size !
  
-There is huge benefit to use ''bfq'' on rotational HDD. +Note: ''recordsize''  / ''volblocksize''  only defines upper limit. Smaller data still can create smaller recordsize (is it true for block?).
-No more huge lags during KVM backups.+
  
-''bfq'' honor ''ionice'' and: +Examples:
-  * kernel ''zvol'' processes have prio ''be/0'' +
-  * kvm processes have prio ''be/4'' +
-  * kvm process during vzdump have ''be/7'' - NOTE: only with patched version of kvm: ''pve-qemu-kvm'' >= ''8.1.5-6''.+
  
-===== HDD =====+  * 16kB for MySQL/InnoDB 
 +  * 128kB for rotational HDDs
  
-[[https://github.com/openzfs/zfs/discussions/14916|ZFS Send & RaidZ - Poor performance on HDD #14916]]+Check real usage by histogram:
  
 <code bash> <code bash>
-cat /sys/module/zfs/parameters/zfs_vdev_async_write_max_active  +zpool iostat -r 
-echo 2 > /sys/module/zfs/parameters/zfs_vdev_async_write_max_active  +
-cat /sys/module/zfs/parameters/zfs_vdev_async_write_max_active +
-</code>+
  
-Use huge record size - it can help on SMR drives. Note: it only make sense for ZFS file system. Cannot be applied on ZVOL. 
-<code bash> 
-zfs set recordsize=1M hddpool/data 
-zfs set recordsize=1M hddpool/vz 
 </code> </code>
  
-For ZVOLs: [[https://openzfs.github.io/openzfs-docs/Performance%20and%20Tuning/Workload%20Tuning.html#zvol-volblocksize|zvol volblocksize]]+===== zvol for guest =====
  
-[[https://blog.guillaumematheron.fr/2023/500/change-zfs-volblock-on-a-running-proxmox-vm/|Change ZFS volblock on a running Proxmox VM]]+  * match volblock size to guest block size 
 +  * do not use guest CoW filesystem on CoW (ZFS) 
 +  * do not use qcow2 files on ZFS 
 +  * use 2 zvols per guest FS - one for storage and second one for journal
  
-<code bash> +===== Tune L2ARC for backups =====
-zfs create -s -V 40G hddpool/data/vm-156-disk-0-16k -o volblock=16k +
-dd if=/dev/zvol/hddpool/data/vm-156-disk-0 of=/dev/zvol/hddpool/data/vm-156-disk-0-16k bs=1M status=progress conv=sparse +
-zfs rename /dev/zvol/hddpool/data/vm-156-disk-0 /dev/zvol/hddpool/data/vm-156-disk-0-backup +
-zfs rename /dev/zvol/hddpool/data/vm-156-disk-0-16k /dev/zvol/hddpool/data/vm-156-disk-0 +
-</code>+
  
 +When huge portion of data are written (new backups) or read (backup verify) L2ARC is constantly written with current data. To change this behaviour to cache only ''Most Frequent Use'':
 +
 +<file conf /etc/modprobe.d/zfs.conf>
 +options zfs l2arc_mfuonly=1 l2arc_noprefetch=0
 +
 +
 +</file>
 +
 +Explanation:
 +
 +  * [[https://openzfs.github.io/openzfs-docs/Performance%20and%20Tuning/Module%20Parameters.html#l2arc-mfuonly|l2arc_mfuonly]] Controls whether only MFU metadata and data are cached from ARC into L2ARC. This may be desirable to avoid wasting space on L2ARC when reading/writing large amounts of data that are not expected to be accessed more than once. By default both MRU and MFU data and metadata are cached in the L2ARC.
 +  * [[https://openzfs.github.io/openzfs-docs/Performance%20and%20Tuning/Module%20Parameters.html#l2arc-noprefetch|l2arc_noprefetch]] Disables writing prefetched, but unused, buffers to cache devices. Setting to 0 can increase L2ARC hit rates for workloads where the ARC is too small for a read workload that benefits from prefetching. Also, if the main pool devices are **very slow**, setting to 0 can improve some workloads such as **backups**.
  
  
-Use ''bfq'' is mandator. See [[#my findings]]. 
  
  
Line 83: Line 104:
 # ONLY for SSD/NVM devices: # ONLY for SSD/NVM devices:
 zfs set logbias=throughput <pool>/postgres zfs set logbias=throughput <pool>/postgres
 +
 +
 </code> </code>
  
Line 88: Line 111:
  
 By default ZFS can sue 50% of RAM for ARC cache: By default ZFS can sue 50% of RAM for ARC cache:
 +
 <code bash> <code bash>
 # apt install zfsutils-linux # apt install zfsutils-linux
  
-# arcstat +# zarcstat
     time  read  miss  miss%  dmis  dm%  pmis  pm%  mmis  mm%  size     c  avail     time  read  miss  miss%  dmis  dm%  pmis  pm%  mmis  mm%  size     c  avail
 16:47:26     3     0      0     0    0     0    0     0    0   15G   15G   1.8G 16:47:26     3     0      0     0    0     0    0     0    0   15G   15G   1.8G
Line 97: Line 121:
  
 <code bash> <code bash>
-# arc_summary +# zarcsummary -s arc
  
 ARC size (current):                                    98.9 %   15.5 GiB ARC size (current):                                    98.9 %   15.5 GiB
Line 111: Line 135:
 </code> </code>
  
-ARC size can be tuned by settings ''zfs'' kernel module parameters ([[https://openzfs.github.io/openzfs-docs/Performance%20and%20Tuning/Module%20Parameters.html#zfs-arc-max|Module Parameters]]):+ARC size can be tuned by settings ''zfs''  kernel module parameters ([[https://openzfs.github.io/openzfs-docs/Performance%20and%20Tuning/Module%20Parameters.html#zfs-arc-max|Module Parameters]]): 
   * ''zfs_arc_max'': Maximum size of ARC in bytes. If set to 0 then the maximum size of ARC is determined by the amount of system memory installed (50% on Linux)   * ''zfs_arc_max'': Maximum size of ARC in bytes. If set to 0 then the maximum size of ARC is determined by the amount of system memory installed (50% on Linux)
-  * ''zfs_arc_min'': Minimum ARC size limit. When the ARC is asked to shrink, it will stop shrinking at ''c_min'' as tuned by ''zfs_arc_min''. +  * ''zfs_arc_min'': Minimum ARC size limit. When the ARC is asked to shrink, it will stop shrinking at ''c_min''  as tuned by ''zfs_arc_min''. 
-  * ''zfs_arc_meta_limit_percent'': Sets the limit to ARC metadata, arc_meta_limit, as a percentage of the maximum size target of the ARC, ''c_max''. Default is 75.+  * ''zfs_arc_meta_balance'': Balance between metadata and data on ghost hits. Values above 100 increase metadata caching by proportionally reducing effect of ghost data hits on target data/metadata rate. [[https://openzfs.github.io/openzfs-docs/man/master/4/zfs.4.html#zfs_arc_meta_balance]]
  
 Proxmox recommends following [[https://pve.proxmox.com/wiki/ZFS_on_Linux#sysadmin_zfs_limit_memory_usage|rule]]: Proxmox recommends following [[https://pve.proxmox.com/wiki/ZFS_on_Linux#sysadmin_zfs_limit_memory_usage|rule]]:
 +<code>
  
-  As a general rule of thumb, allocate at least 2 GiB Base + 1 GiB/TiB-Storage+As a general rule of thumb, allocate at least 2 GiB Base + 1 GiB/TiB-Storage 
 + 
 +</code>
  
 ==== Examples ==== ==== Examples ====
-   + 
-Set ''zfs_arc_max'' to 4GB and ''zfs_arc_min'' to 128MB:+Set ''zfs_arc_max''  to 4GB and ''zfs_arc_min''  to 128MB: 
 <code bash> <code bash>
 echo "$[4 * 1024*1024*1024]" >/sys/module/zfs/parameters/zfs_arc_max echo "$[4 * 1024*1024*1024]" >/sys/module/zfs/parameters/zfs_arc_max
Line 129: Line 158:
  
 Make options persistent: Make options persistent:
-<file /etc/modprobe.d/zfs.conf>+ 
 +<code etcmodprobedzfsconf>
 options zfs zfs_prefetch_disable=1 options zfs zfs_prefetch_disable=1
 options zfs zfs_arc_max=4294967296 options zfs zfs_arc_max=4294967296
 options zfs zfs_arc_min=134217728 options zfs zfs_arc_min=134217728
 options zfs zfs_arc_meta_limit_percent=75 options zfs zfs_arc_meta_limit_percent=75
-</file>+</code>
  
 and ''update-initramfs -u'' and ''update-initramfs -u''