Re: [doc fix] Correct calculation of vm.nr_hugepages

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [doc fix] Correct calculation of vm.nr_hugepages
Date: 2018-02-22 14:25:59
Message-ID: CA+TgmobDRXzLJ_u4pYD4UK=rYjUb_B4brO-5zPRO3fYX8duVNg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 21, 2018 at 3:28 PM, Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> On Wed, Feb 21, 2018 at 03:14:57PM -0500, Robert Haas wrote:
>> On Mon, Feb 19, 2018 at 9:43 PM, Tsunakawa, Takayuki
>> <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> wrote:
>> > Thanks, I'd like to take this.
>>
>> Why are these values so large? The example in the documentation shows
>> 6490428 kB, and in my test I got 8733888 kB. But 8733888 kB = 8.3 TB!
>> 8.3 GB would make sense, but 8.3 TB does not.
>
> pryzbyj(at)pryzbyj:~$ units -t -v 8733888kB GiB
> 8733888kB = 8.1340671 GiB

Sigh. It would be nice if I were less stupid.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2018-02-22 14:32:32 Re: pgsql: Avoid valgrind complaint about write() of uninitalized bytes.
Previous Message Robert Haas 2018-02-22 14:25:28 Re: Possible performance regression in version 10.1 with pgbench read-write tests.