Re: Allow a per-tablespace effective_io_concurrency setting - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: Allow a per-tablespace effective_io_concurrency setting
Date
Msg-id CAHyXU0zmLcqE_=e50ZyhReNGy_AcEwTCPdcOfw_BS3w5Ssa-BQ@mail.gmail.com
Whole thread Raw
In response to Re: Allow a per-tablespace effective_io_concurrency setting  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
On Wed, Sep 2, 2015 at 4:31 PM, Josh Berkus <josh@agliodbs.com> wrote:
> 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.

That's the exact opposite of my findings on intel S3500 (see:
http://www.postgresql.org/message-id/CAHyXU0yiVvfQAnR9cyH=HWh1WbLRsioe=mzRJTHwtr=2azsTdQ@mail.gmail.com).

merlin



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: pgbench stats per script & other stuff
Next
From: Jeff Janes
Date:
Subject: Re: Allow a per-tablespace effective_io_concurrency setting