Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mPsRA-00039r-Fd for pgsql-hackers@arkaria.postgresql.org; Mon, 13 Sep 2021 20:20:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mPsR9-0002CM-9h for pgsql-hackers@arkaria.postgresql.org; Mon, 13 Sep 2021 20:20:19 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mPsR8-0002CE-W7 for pgsql-hackers@lists.postgresql.org; Mon, 13 Sep 2021 20:20:19 +0000 Received: from mail-il1-x12e.google.com ([2607:f8b0:4864:20::12e]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mPsR2-0006gh-Ij for pgsql-hackers@postgresql.org; Mon, 13 Sep 2021 20:20:18 +0000 Received: by mail-il1-x12e.google.com with SMTP id w1so11490585ilv.1 for ; Mon, 13 Sep 2021 13:20:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=UyeC/B0HJMniSCLEeQjrUVV4zlDj1Fdo9bQx9xdaFvE=; b=GlB0xCx69PvKt2KiN3kmwXJJQk0FRDfwy/RLj6dw7zu3+uCHyghG2PN+0OE9XdJLSk I0Yvs3dmUMG2+UvawETt50IZARCjbDmLjli9zt0fGO4ubQejQ7KXFq8m8pwHqb7A2b/i gaGM+ziG0VDnydbNBe/JXIt1c+9OUsuEVAfzkPGYPK1dbCouwHELtDVUDOUdmnMoTvWB fd7qrH7+PxovDMlI5lo8PB0Pq9CGdx2VoQvFyKd9quyt3oaLWBzjiZ1J4Q4a78mRJzsF EqwZD/6anjjgg6Bu02zu54QyY1xWm2lBo9CcAyfWVUZzRv3vRmsMpAO8aA5ZgmU7vV/f ZX5g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=UyeC/B0HJMniSCLEeQjrUVV4zlDj1Fdo9bQx9xdaFvE=; b=07YQfgVw3PrhIjqrlBjIkehW2S/7al5sYocJbWG9D1Sc7O0nvsj33fbJMbYPSWDsg2 hxUJ6sdcaRBK7mFTuRrfijTJEJuw/CZnxJ00RoxhqUGuDI1k6fETgrHljvr8+IYxINDH 0yOR5wH0BXbA+Hg3Mlo0rxm+2NlE7XmmE0l2B96A8hXK5RY8v8nmTLZ6XSREPmDrGjoQ dSni0xwCmoAMKGbgJU1oCJ3NnPia8VnS1Q0ODK+J135DtmeWOnNH2RhumLCa5jeaflVE KFurNBFE7dAQ7uLywEU89mIcpRZq3AglRNBBS1CvFdwjtFKDiCrq42149vp91FcLWXBk fDMQ== X-Gm-Message-State: AOAM530ZiAPwJXnuixH2K/2VwkW52Ya88uoWSf/LcPwtuLCM5aLtLOpQ BK6+x4lBhz6ToIbl6MoFNqN6cTWaw1dz/0wgsdw= X-Google-Smtp-Source: ABdhPJy84pSmcBkgz4rNVXIF9+LgumDMg3OrtPLWmSnIt7SD7qjg7gUDQD4pXThdf4G9o0+oFiz727EBSmWvBCKKVKo= X-Received: by 2002:a05:6e02:1bc9:: with SMTP id x9mr9255725ilv.314.1631564411360; Mon, 13 Sep 2021 13:20:11 -0700 (PDT) MIME-Version: 1.0 References: <7ED221D0-0D75-46F8-8D6C-8AF70D8EABE7@amazon.com> <89EFD5FB-3C28-459C-9D6D-C9F93F7C2A54@amazon.com> <578A8F79-FD13-4408-865F-4D31EE5D8123@amazon.com> <4cc5b434-b174-9aae-197b-737db6cac4e3@oss.nttdata.com> <6AE0285D-0917-4C05-B6AA-4AEDD2FCBA52@amazon.com> <7E4B78B7-4B8C-41D1-862D-B0BDC3432F83@amazon.com> In-Reply-To: From: Robert Haas Date: Mon, 13 Sep 2021 16:20:00 -0400 Message-ID: Subject: Re: Estimating HugePages Requirements? To: "Bossart, Nathan" Cc: Michael Paquier , Fujii Masao , Justin Pryzby , Andres Freund , Magnus Hagander , Mark Dilger , Don Seiler , "pgsql-hackers@postgresql.org" Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Sep 13, 2021 at 2:49 PM Bossart, Nathan wrote: > Yeah, I agree. What about > huge_pages_needed_for_shared_memory_size or > huge_pages_needed_for_main_shared_memory? I'm still not stoked about > using "required" or "needed" in the name, as it sounds like huge pages > must be allocated for the server to run, which is only true if > huge_pages=on. I haven't thought of a better word to use, though. I prefer the first of those to the second. I don't find it particularly better or worse than my previous suggestion of shared_memory_size_in_huge_pages. -- Robert Haas EDB: http://www.enterprisedb.com