From f3ed8a80ab56bd29ce7302b5431334f04db10725 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=B6rg=20Thalheim?= Date: Mon, 30 Jan 2017 12:25:04 +0100 Subject: [PATCH] zfs: fixed assumptions about thin provisioning unlike lvm thin provisioning is fast and does not slow down the filesystem --- engine/userguide/storagedriver/zfs-driver.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/engine/userguide/storagedriver/zfs-driver.md b/engine/userguide/storagedriver/zfs-driver.md index 30ef08c7ae..3ef63c8542 100644 --- a/engine/userguide/storagedriver/zfs-driver.md +++ b/engine/userguide/storagedriver/zfs-driver.md @@ -315,12 +315,6 @@ storage media such as solid state devices (SSD). However, if you only have a limited amount of SSD storage available it is recommended to place the ZIL on SSD. -- **Use Data Volumes**. Data volumes provide the best and most predictable -performance. This is because they bypass the storage driver and do not incur -any of the potential overheads introduced by thin provisioning and -copy-on-write. For this reason, you should place heavy write workloads on data -volumes. - ## Limiting your container's writable storage quota If you want to implement a quota on a per-image/dataset basis, you can use