[ARVADOS] updated: bc9845761c44beecdd046620694f6d88af0e32fd

[git at public.curoverse.com]

Summary of changes:
 doc/install/install-keepstore.html.textile.liquid | 2 ++
 1 file changed, 2 insertions(+)

       via  bc9845761c44beecdd046620694f6d88af0e32fd (commit)
       via  aed1bd10f559fd5428bc1c259d324aa78a2de511 (commit)
      from  ef3e45fcc338a85432c207685567385972f79ee6 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.


commit bc9845761c44beecdd046620694f6d88af0e32fd
Merge: ef3e45f aed1bd1
Author: Ward Vandewege <ward at curoverse.com>
Date:   Wed Jan 20 11:26:16 2016 -0500

    Merge branch '8248-explain-serialize'
    
    closes #8248


commit aed1bd10f559fd5428bc1c259d324aa78a2de511
Author: Ward Vandewege <ward at curoverse.com>
Date:   Wed Jan 20 11:25:20 2016 -0500

    Doc improvement: explain in more detail what the -serialize argument to
    keepstore does.
    
    closes #8248

diff --git a/doc/install/install-keepstore.html.textile.liquid b/doc/install/install-keepstore.html.textile.liquid
index efeff65..f5e8193 100644
--- a/doc/install/install-keepstore.html.textile.liquid
+++ b/doc/install/install-keepstore.html.textile.liquid
@@ -116,6 +116,8 @@ 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 at .
 
+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 at .
+
 h3. Set up additional servers
 
 Repeat the above sections to prepare volumes and bring up supervised services on each Keepstore server you are setting up.

-----------------------------------------------------------------------


hooks/post-receive
--