| From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
|---|---|
| To: | Lucas Possamai <drum(dot)lucas(at)gmail(dot)com> |
| Cc: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Increased I/O / Writes |
| Date: | 2016-05-23 21:40:51 |
| Message-ID: | CACjxUsOqo5pVFj23A14KZRKmJqaKDe-2mb1NaB_D1dfwN0LQMw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, May 23, 2016 at 4:32 PM, Lucas Possamai <drum(dot)lucas(at)gmail(dot)com> wrote:
> The spikes were happening because, after the reboot, the HUGE PAGES were
> enabled.
>
> After disabling them, all got back to normal.
Since you said earlier you were on PostgreSQL version 9.2, you must
be talking about transparent huge pages. Yeah, be sure those are
configured to be disabled in a way that "sticks" on your OS. When
you get to version 9.4 you will notice that we support huge pages
directly. That would be expected to work without problems even
though TRANSPARENT huge pages are debilitating.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lucas Possamai | 2016-05-23 21:44:06 | Re: Increased I/O / Writes |
| Previous Message | Lucas Possamai | 2016-05-23 21:40:15 | Re: Function PostgreSQL 9.2 |