Re: effective_io_concurrency on EBS/gp2 - Mailing list pgsql-performance

From Jeff Janes
Subject Re: effective_io_concurrency on EBS/gp2
Date
Msg-id CAMkU=1xE2mqf5Fpn8rXAWZEKr0QBKbnWOs4djZOt6ye4gYWMtw@mail.gmail.com
Whole thread Raw
In response to effective_io_concurrency on EBS/gp2  (Vitaliy Garnashevich <vgarnashevich@gmail.com>)
List pgsql-performance
On Wed, Jan 31, 2018 at 4:03 AM, Vitaliy Garnashevich <vgarnashevich@gmail.com> wrote:

The results look really confusing to me in two ways. The first one is that I've seen recommendations to set effective_io_concurrency=256 (or more) on EBS.

I would not expect this to make much of a difference on a table which is perfectly correlated with the index.  You would have to create an accounts table which is randomly ordered to have a meaningful benchmark of the eic parameter.

I don't know why the default for eic is 1.  It seems like that just turns on the eic mechanism, without any hope of benefiting from it.

Cheers,

Jeff

pgsql-performance by date:

Previous
From: Vitaliy Garnashevich
Date:
Subject: Re: effective_io_concurrency on EBS/gp2
Next
From: pavan95
Date:
Subject: Re: 8.2 Autovacuum BUG ?