mirror of https://github.com/docker/docs.git
zfs: fixed assumptions about thin provisioning
unlike lvm thin provisioning is fast and does not slow down the filesystem
This commit is contained in:
parent
28659b7a38
commit
f3ed8a80ab
|
@ -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
|
limited amount of SSD storage available it is recommended to place the ZIL on
|
||||||
SSD.
|
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
|
## Limiting your container's writable storage quota
|
||||||
|
|
||||||
If you want to implement a quota on a per-image/dataset basis, you can use
|
If you want to implement a quota on a per-image/dataset basis, you can use
|
||||||
|
|
Loading…
Reference in New Issue