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-ASN: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-3.8 required=3.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id DC9AD1F8C7 for ; Thu, 29 Jul 2021 21:24:47 +0000 (UTC) Received: by mail-qt1-x82f.google.com with SMTP id t18so4980863qta.8 for ; Thu, 29 Jul 2021 14:24:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=ht7bzmsUTkSWLbooF5NwkfuYP+Lit8GyXVHsFpdmGgc=; b=EfQJ8/srpYHNwvSM7Z41QGIIaDBLPDgJA23gGzgRc/UrKQgdGy64r1eJaOSEDnsCdw 4CHYLStl6psvQd/1tbOU2p6GlWopUp3P3ZRqYJHVokbTA5Z/EPr4vmnpFj0G28APHfeq hKYcaP8+vUlI17jATb4rHaJ4JkmeeqiZc/gvs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=ht7bzmsUTkSWLbooF5NwkfuYP+Lit8GyXVHsFpdmGgc=; b=F3jSyslf2iQ5SW7gaIOwJBKRC+0nHTgQeZhHbJM38OmetEmcr9CW+i1VvCqb1l5wu9 VqPpFsCNFzvzM0dXTRfcUdUdfH0MKyieuFVHwAcjaie1p4krnxEsnllsYLUxFDvyTNel ae4u1VvwSr7kSHwfeTjlVViXPVLn98eKq9Sl3Epr3VNlTqvM9CZ0KnsaAfXBgoGdR+hm MqJOy29pDkvLredilyUTUgkpYbYI+1w+iT0oFDCrKTsYXvYxAsl32Xn12hqyj7Qt+ysD j4Oc8LMW8et4oSrFjYhqngXBajlvnl0dVrBI+PhwCAXziPCphPOlBP+bC2tUtMEmWELn 0Bqg== X-Gm-Message-State: AOAM533ASiP+QXlw+ifxQxj9FWM42x0VyYHCvyVWBb58F6QM30kGncPC YWYDXZuiUovh0YEzOJde1wIYBA== X-Google-Smtp-Source: ABdhPJx3TfQ8CekDzvaZcKgoeygAgbotfpvnVGpf3EnsES9iWaIIxThaSWq/AoHSJ0mBF0nFcv2ljQ== X-Received: by 2002:ac8:7e86:: with SMTP id w6mr6072329qtj.194.1627593886547; Thu, 29 Jul 2021 14:24:46 -0700 (PDT) Received: from nitro.local ([89.36.78.230]) by smtp.gmail.com with ESMTPSA id n14sm1826926qti.47.2021.07.29.14.24.46 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 29 Jul 2021 14:24:46 -0700 (PDT) Date: Thu, 29 Jul 2021 17:24:44 -0400 From: Konstantin Ryabitsev To: Eric Wong Cc: meta@public-inbox.org Subject: Re: --batch-size and --jobs combination Message-ID: <20210729212444.3jnmaq4vo4dnudk3@nitro.local> References: <20210729202836.7qdwxojjel6jmxh6@nitro.local> <20210729211321.GA23521@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20210729211321.GA23521@dcvr> List-Id: On Thu, Jul 29, 2021 at 09:13:21PM +0000, Eric Wong wrote: > jobs will be bound by I/O capability for your case. SATA-2 vs > SATA-3 vs NVME will have a notable difference, as does the > quality of the device (MLC, TLC, QLC; cache/controller). So, on these systems with large lvmcache disks, large --jobs number isn't really going to help, right? Disk performance is not great, since these systems are continuously serving traffic for mirrors.kernel.org, but writes are spread across RAID-6, so not sure --sequential-shard will do much difference. Let me try "--jobs=2 --batch-size=1g --no-fsync" for the initial index. There's 128G of RAM on this system, so it should be able to take that easily. I didn't use --no-fsync due to the admonition in the manpages that it probably will result in worse performance with a large --batch-size, but if you say it's going to likely help, I'm willing to try that out. Thanks for your help! -K