From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 4E18B1F66E for ; Thu, 13 Aug 2020 08:04:04 +0000 (UTC) From: Eric Wong To: meta@public-inbox.org Subject: [PATCH] grok-pull.post_update_hook: favor --sequential-shard for HDD Date: Thu, 13 Aug 2020 08:04:04 +0000 Message-Id: <20200813080404.27513-1-e@yhbt.net> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit List-Id: --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