From 064811ca0fa11586159d0049476e64b70f7e34d1 Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Thu, 13 Aug 2020 08:04:04 +0000 Subject: [PATCH] grok-pull.post_update_hook: favor --sequential-shard for HDD --sequential-shard offers better performance on HDD than -j0 since the on-disk active set can be kept small (with -j $HIGH_NUM). --batch-size can also be helpful for systems with much RAM. --- examples/grok-pull.post_update_hook.sh | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/examples/grok-pull.post_update_hook.sh b/examples/grok-pull.post_update_hook.sh index 092ca283..1f51140f 100755 --- a/examples/grok-pull.post_update_hook.sh +++ b/examples/grok-pull.post_update_hook.sh @@ -124,7 +124,9 @@ then : v2 inboxes may be init-ed with an empty msgmap ;; *) - # if on HDD and limited RAM, add `-j0' w/ public-inbox 1.6.0+ + # if on HDD and limited RAM, add `--sequential-shard' + # and possibly a large `--batch-size' if you have much + # memory in public-inbox 1.6.0+ $EATMYDATA public-inbox-index -v "$inbox_dir" ;; esac -- 2.44.0