From e13caf8cda321b07ce2bbe6e68d0e07c1d856a58 Mon Sep 17 00:00:00 2001 From: Ward Vandewege Date: Wed, 20 Jan 2016 13:19:58 -0500 Subject: [PATCH] Fix typo. refs #8248 --- doc/install/install-keepstore.html.textile.liquid | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/install/install-keepstore.html.textile.liquid b/doc/install/install-keepstore.html.textile.liquid index f5e8193cd6..2e7382bf1e 100644 --- a/doc/install/install-keepstore.html.textile.liquid +++ b/doc/install/install-keepstore.html.textile.liquid @@ -116,7 +116,7 @@ The @-max-buffers@ argument limits keepstore's memory usage. It should be set su If you want access control on your Keepstore server(s), you must specify the @-enforce-permissions@ flag and provide a signing key. The @-blob-signing-key-file@ argument should be a file containing a long random alphanumeric string with no internal line breaks (it is also possible to use a socket or FIFO: keepstore reads it only once, at startup). This key must be the same as the @blob_signing_key@ configured in the "API server's":install-api-server.html configuration file, @/etc/arvados/api/application.yml@. -The @-serialize=true@ (default: @false@) argument limits keepstore to one reader/writer process per storage partition. This avoids trashing by allowing the storage device underneath the storage partition to do read/write operations sequentially. Enabling @-serialize@ can improve Keepstore performance if the storage partitions map 1:1 to physical disks that are dedicated to Keepstore, particularly so for mechanical disks. In some cloud environments, enabling @-serialize@ has also also proven to be beneficial for performance, but YMMV. If your storage partition(s) are backed by network or RAID storage that can handle many simultaneous reader/writer processes without trashing, you probably do not want to set @-serialize@. +The @-serialize=true@ (default: @false@) argument limits keepstore to one reader/writer process per storage partition. This avoids thrashing by allowing the storage device underneath the storage partition to do read/write operations sequentially. Enabling @-serialize@ can improve Keepstore performance if the storage partitions map 1:1 to physical disks that are dedicated to Keepstore, particularly so for mechanical disks. In some cloud environments, enabling @-serialize@ has also also proven to be beneficial for performance, but YMMV. If your storage partition(s) are backed by network or RAID storage that can handle many simultaneous reader/writer processes without thrashing, you probably do not want to set @-serialize@. h3. Set up additional servers -- 2.30.2