diff options
| author | Colin Walters <walters@verbum.org> | 2020-07-16 21:13:36 +0000 |
|---|---|---|
| committer | Colin Walters <walters@verbum.org> | 2020-07-18 14:59:01 +0000 |
| commit | a615d35762be74b6407bfcbdde5387f84dd151cf (patch) | |
| tree | 8f9ab26b0be8d7c50446c1501b932065be01242a /man/ostree.repo-config.xml | |
| parent | 4752dd02cfddd3f7c102e7fdd4dcca9a1aeee1a1 (diff) | |
| download | ostree-a615d35762be74b6407bfcbdde5387f84dd151cf.tar.gz | |
pull: Add --per-object-fsync
This is the opposite of
https://github.com/ostreedev/ostree/issues/1184
Motivated by OpenShift seeing etcd performance issues during
OS updates: https://github.com/openshift/machine-config-operator/issues/1897
Basically, if we switch to invoking `fsync()` as we go, it makes
ostree performance worse (in my tests, 31s to write 2G versus 7s if we
delay sync) but it avoids *huge* outliers in `fsync()` time for etcd.
Diffstat (limited to 'man/ostree.repo-config.xml')
| -rw-r--r-- | man/ostree.repo-config.xml | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/man/ostree.repo-config.xml b/man/ostree.repo-config.xml index 90ac9083..7a01fc01 100644 --- a/man/ostree.repo-config.xml +++ b/man/ostree.repo-config.xml @@ -128,6 +128,18 @@ Boston, MA 02111-1307, USA. </varlistentry> <varlistentry> + <term><varname>per-object-fsync</varname></term> + <listitem><para>By default, OSTree will batch fsync() after + writing everything; however, this can cause latency spikes + for other processes which are also invoking fsync(). + Turn on this boolean to reduce potential latency spikes, + at the cost of slowing down OSTree updates. You most + likely want this on by default for "background" OS updates. + </para> + </listitem> + </varlistentry> + + <varlistentry> <term><varname>min-free-space-percent</varname></term> <listitem> <para> |