diff options
| author | Eric Wong <e@yhbt.net> | 2020-08-15 05:21:02 +0000 |
|---|---|---|
| committer | Eric Wong <e@yhbt.net> | 2020-08-16 20:22:06 +0000 |
| commit | 99850fabd5fc628ab29c718e9d7de09b8114b208 (patch) | |
| tree | 0ca9e5600ef35999dd7494cefda4e73c7622a2f0 /Documentation/public-inbox-v2-format.pod | |
| parent | 064811ca0fa11586159d0049476e64b70f7e34d1 (diff) | |
| download | public-inbox-99850fabd5fc628ab29c718e9d7de09b8114b208.tar.gz | |
Determining storage device speed and latencies doesn't seem portable or even possible with the wide variety of storage layers in use. This means we need to write a tuning document and hope users read and improve on it :P
Diffstat (limited to 'Documentation/public-inbox-v2-format.pod')
| -rw-r--r-- | Documentation/public-inbox-v2-format.pod | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/public-inbox-v2-format.pod b/Documentation/public-inbox-v2-format.pod index 6876989c..86a9b8f2 100644 --- a/Documentation/public-inbox-v2-format.pod +++ b/Documentation/public-inbox-v2-format.pod @@ -117,9 +117,9 @@ Rotational storage devices perform significantly worse than solid state storage for indexing of large mail archives; but are fine for backup and usable for small instances. -As of public-inbox 1.6.0, the C<--sequential-shard> option of -L<public-inbox-index(1)> may be used with a high shard count -to ensure individual shards fit into page cache when the entire +As of public-inbox 1.6.0, the C<publicInbox.indexSequentialShard> +option of L<public-inbox-index(1)> may be used with a high shard +count to ensure individual shards fit into page cache when the entire Xapian DB cannot. Our use of the L</OVERVIEW DB> requires Xapian document IDs to |