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.

diff --git a/examples/grok-pull.post_update_hook.sh b/examples/grok-pull.post_update_hook.sh
index 092ca283b30e289165cf86d279d22fb8a0ac1dbe..1f51140ffbd139b57d41065e619a4115173ee841 100755 (executable)
--- 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