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 1mPoGj-0000ZJ-CU for pgsql-hackers@arkaria.postgresql.org; Mon, 13 Sep 2021 15:53:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mPoGi-00082i-CI for pgsql-hackers@arkaria.postgresql.org; Mon, 13 Sep 2021 15:53:16 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mPoDd-0001xU-Pe for pgsql-hackers@lists.postgresql.org; Mon, 13 Sep 2021 15:50:05 +0000 Received: from mail-io1-xd33.google.com ([2607:f8b0:4864:20::d33]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mPoDb-0001ca-7Y for pgsql-hackers@postgresql.org; Mon, 13 Sep 2021 15:50:05 +0000 Received: by mail-io1-xd33.google.com with SMTP id n24so12698242ion.10 for ; Mon, 13 Sep 2021 08:50:03 -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=SCnmyvUjXvY5bGTp6bdZ+aMnrOuCa8psb9IETBVXYZA=; b=g/76JOiMFOv3YclO7XptUIzzEfCuaq6U4upk2pORUCN/xTiCSkORdDEa1MYmMgXXrK ivmpUw3w6THstQan8NkS0I5fjFmmfSAsvCYG3THyB+YzeeV23h1dGdJhOo+v1PPizNMb 6bJpjEPE3ZclEDZ5qMmBIKdETZWWubsyxDhlJfsDWHvb3f0qslrW6Fy167F/8EjTINog o7ydVEeAWBQYKmWoN5itOLTXwCEzu7bxZU/YzrkcVuozAdgSgcdnFB1BkO0Vay2jAGYW j1EIwo8FvDeWr+iU5WgW3Q485Yone5DkfFD3Metmubufdkv8IPGffF6OXWozLlQJ1Vsl Ageg== 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=SCnmyvUjXvY5bGTp6bdZ+aMnrOuCa8psb9IETBVXYZA=; b=2GYCT9SX1C0//MLcYrPbhnukNkjvYLfcs+RGu2rH0/uFSoJBzJZQ7Aqd9Ef8sct+lU miR9KEgh3P1xNWkjoXxoRhwLDBfJHPU8uJf/bFNpMoPNXsidrfN9P7qk65jshUFPuArA O89qvfHdh0JLfF7z9CZAxgxldwSq89/TLWBegb/Lpf7l3DsYRsv5/WgoDfNDonvbYoCu lafPHkS/5OSD3aFZ8VPVhEw+0cKIgiTs5Ok9s7F+R4sseHBJHA6/lE1I03YsE3NgXPQN GYjHh0Vnl1UA5osZYsl4XUu5ceD9bu1RBskMMvEEbC+07zAoZf7lw8EMGfxFNHlaB+zz ZTGw== X-Gm-Message-State: AOAM530rdI8MgLYH8sl63Je1xuRHnk5wIAI2j3cNq8pG6ua7WaFw6J9x 4d9h9X7AvEaeAD36ytx3EzYKHme6mn3N/tHeKV8= X-Google-Smtp-Source: ABdhPJyVOG5TPvC7WaJFrWWSkIbioPYGCE3IIfqPXp/QIlv1/0VjBvm4i/o83yWzNDf1VWhBjSf4HqPkkvwy0FocIGY= X-Received: by 2002:a6b:5a1a:: with SMTP id o26mr9670649iob.40.1631548201076; Mon, 13 Sep 2021 08:50:01 -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: <7E4B78B7-4B8C-41D1-862D-B0BDC3432F83@amazon.com> From: Robert Haas Date: Mon, 13 Sep 2021 11:49:49 -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 Fri, Sep 10, 2021 at 7:43 PM Bossart, Nathan wrote: > > shared_memory_size_in_huge_pages? It's kinda long, but a long name > > that you can understand without reading the docs is better than a > > short one where you can't. > > I think that's an improvement. The only other idea I have at the > moment is num_huge_pages_required_for_shared_memory. Hmm, that to me sounds like maybe only part of shared memory uses huge pages and maybe we're just giving you the number required for that part. I realize that it doesn't work that way but I don't know if everyone will. -- Robert Haas EDB: http://www.enterprisedb.com