Re: Allow a per-tablespace effective_io_concurrency setting

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Allow a per-tablespace effective_io_concurrency setting
Date: 2015-09-02 16:45:56
Message-ID: 20150902164556.GF5286@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

On 2015-09-02 18:06:54 +0200, Tomas Vondra wrote:
> Maybe the best thing we can do is just completely abandon the "number of
> spindles" idea, and just say "number of I/O requests to prefetch". Possibly
> with an explanation of how to estimate it (devices * queue length).

I think that'd be a lot better.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2015-09-02 17:10:51 Re: WIP: Make timestamptz_out less slow.
Previous Message Christopher Browne 2015-09-02 16:45:26 Re: Proposal: Implement failover on libpq connect level.

Browse pgsql-performance by date

  From Date Subject
Next Message Greg Stark 2015-09-02 18:49:13 Re: Allow a per-tablespace effective_io_concurrency setting
Previous Message Tomas Vondra 2015-09-02 16:06:54 Re: Allow a per-tablespace effective_io_concurrency setting