| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Allow a per-tablespace effective_io_concurrency setting |
| Date: | 2015-09-02 21:31:35 |
| Message-ID: | 55E76AB7.4030306@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
On 09/02/2015 02:25 PM, Tomas Vondra wrote:
>
> As I explained, spindles have very little to do with it - you need
> multiple I/O requests per device, to get the benefit. Sure, the DBAs
> should know how many spindles they have and should be able to determine
> optimal IO depth. But we actually say this in the docs:
My experience with performance tuning is that values above 3 have no
real effect on how queries are executed.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-09-02 21:34:57 | Re: exposing pg_controldata and pg_config as functions |
| Previous Message | Joe Conway | 2015-09-02 21:31:20 | Re: exposing pg_controldata and pg_config as functions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2015-09-02 21:58:33 | Re: Allow a per-tablespace effective_io_concurrency setting |
| Previous Message | Tomas Vondra | 2015-09-02 21:25:36 | Re: Allow a per-tablespace effective_io_concurrency setting |