| From: | Andrew Kerber <andrew(dot)kerber(at)gmail(dot)com> |
|---|---|
| To: | Lucas Possamai <drum(dot)lucas(at)gmail(dot)com> |
| Cc: | pinker <pinker(at)onet(dot)eu>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Huge Pages - setting the right value |
| Date: | 2017-06-11 22:36:20 |
| Message-ID: | CAJvnOJYKvZ06Yu9Dnnh58tzP4+AvQuzn4hj2LcbmVRnte34UUA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Yes, those should always be disabled using tuned or other methods. Using
tuned is described here (second method). I think the grub.conf method
described is unique to RHEL/OEL/CENTOS.
http://houseofbrick.com/disabling-transparent-hugepages-using-tuned/
On Sun, Jun 11, 2017 at 5:00 PM, Lucas Possamai <drum(dot)lucas(at)gmail(dot)com>
wrote:
>
>
> 2017-06-12 9:52 GMT+12:00 Andrew Kerber <andrew(dot)kerber(at)gmail(dot)com>:
>
>> Was that transparent hugepages or standard hugepages? databases commonly
>> have problems dealing with transparent hugepages.
>>
>>
>
>
> IN my case, it was the Transparent Hugepages....
>
>
> Lucas
>
--
Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruno Wolff III | 2017-06-12 01:22:13 | Re: JSON to INT[] or other custom type |
| Previous Message | Lucas Possamai | 2017-06-11 22:00:44 | Re: Huge Pages - setting the right value |