From: | Purav Chovatia <puravc(at)gmail(dot)com> |
---|---|
To: | Arni Kromić <arni(dot)kromic(at)bios-ict(dot)hr> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: IO scheduler recommendation |
Date: | 2019-01-29 07:37:15 |
Message-ID: | CADrzpjF4mwC=ZKWN7UqAi2Lw3PnXqp70b_RBm0=_89qf0YNRSA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi,
IO scheduler is more of an OS thing and not a DB thing. Once the DB (be it
Postgresql or any other) has submitted IO to OS it is up to the OS to make
sure it is written in the fastest possible manner.
In RHEL 6, CFQ was the default and starting RHEL 7, Deadline is the default
(I don’t know exactly why was the default changed). However, across rhel 6
& 7 it is suggested to have deadline for db environments. But what I
separately read is that if the server is a VM, then NOOP is the best
scheduler because you don’t want the VM as well as the host, both to be
scheduling IO which can actually work against. In that case, let the VM not
do anything, instead let the host do the scheduling.
HTH
On Mon, 28 Jan 2019 at 6:05 PM, Arni Kromić <arni(dot)kromic(at)bios-ict(dot)hr> wrote:
> On 21/01/2019 12.04, AB_ba# wrote:
>
> Hello ,
>
> I searched the complete PostgreSQL Documentation but didn't get anything
> with respect to IO scheduler recommendation.
> What is being recommended by PostgreSQL ?
> Which is the best IO scheduler considering the Data is hosted on NFS?
>
>
> --
> Thanks and Regards
> ANUP BHARTI
>
>
> AFAIK, IO scheduler cannot be set for NFS; it's not a real block storage
> device.
>
> --
> Kind Regards,
> Arni Kromić
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | JD | 2019-01-29 08:02:20 | : : How to mask column: : |
Previous Message | Ibrahim Shaame | 2019-01-28 21:11:49 | Re: Building pgadmin4 on Slackware |