| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | AB_ba# <bharti(dot)anup(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: IO scheduler recommendation |
| Date: | 2019-01-21 15:44:51 |
| Message-ID: | df772cb764b99d4f4a454ee307840022c91bcdb6.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
AB_ba# wrote:
> I searched the complete PostgreSQL Documentation but didn't get anything with respect to IO scheduler recommendation.
> What is being recommended by PostgreSQL ?
There is no clear recommendation.
I personally have seen workloads where changing from "cfq" to "deadline"
or "noop" improved performance by a factor of 4, but on many systems "cfq"
seems to be doing at least as good as the others.
I believe that it depends a lot on your hardware configuration and
your workload, and you are best advised to run a realistic load test.
> Which is the best IO scheduler considering the Data is hosted on NFS?
No idea - probably depends on what is behind the NFS.
Make sure to use hard, fg mounts.
If you can, use "jumbo frames" so that an 8KB block can fit into
a single IP frame.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | AB_ba# | 2019-01-22 05:38:06 | Re: IO scheduler recommendation |
| Previous Message | Gary Stainburn | 2019-01-21 15:06:19 | Re: upgrade from FC9 / PG8.3 to C7 / PG 9.6 - utf8 |