Effective IO Concurrency

Started by Nonameover 5 years ago4 messagesgeneral
Jump to latest
#1Noname
luis.roberto@siscobra.com.br

Hi!

In PostgreSQL 13, the way of using effective_io_concurrency has changed. Until v12, I used 200 for this value (using SSD drives). Using the new formula described in [ https://www.postgresql.org/docs/13/release-13.html | https://www.postgresql.org/docs/13/release-13.html ] gives me 1176. However, in the documentation [ https://www.postgresql.org/docs/13/runtime-config-resource.html#GUC-EFFECTIVE-IO-CONCURRENCY | https://www.postgresql.org/docs/13/runtime-config-resource.html#GUC-EFFECTIVE-IO-CONCURRENCY ] it says that the maximum value allowed is 1000.

#2Laurenz Albe
laurenz.albe@cybertec.at
In reply to: Noname (#1)
Re: Effective IO Concurrency

On Mon, 2020-09-14 at 10:39 -0300, luis.roberto@siscobra.com.br wrote:

In PostgreSQL 13, the way of using effective_io_concurrency has changed. Until v12,
I used 200 for this value (using SSD drives). Using the new formula described in
https://www.postgresql.org/docs/13/release-13.html gives me 1176.
However, in the documentation https://www.postgresql.org/docs/13/runtime-config-resource.html#GUC-EFFECTIVE-IO-CONCURRENCY
it says that the maximum value allowed is 1000.

Then use the value 1000...

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com

#3Ron
ronljohnsonjr@gmail.com
In reply to: Laurenz Albe (#2)
Re: Effective IO Concurrency

On 9/14/20 11:03 AM, Laurenz Albe wrote:

On Mon, 2020-09-14 at 10:39 -0300, luis.roberto@siscobra.com.br wrote:

In PostgreSQL 13, the way of using effective_io_concurrency has changed. Until v12,
I used 200 for this value (using SSD drives). Using the new formula described in
https://www.postgresql.org/docs/13/release-13.html gives me 1176.
However, in the documentation https://www.postgresql.org/docs/13/runtime-config-resource.html#GUC-EFFECTIVE-IO-CONCURRENCY
it says that the maximum value allowed is 1000.

Then use the value 1000...

I think he means that the formula should take that into account.

--
Angular momentum makes the world go 'round.

#4Noname
luis.roberto@siscobra.com.br
In reply to: Ron (#3)
Re: Effective IO Concurrency

De: "Ron" <ronljohnsonjr@gmail.com>
Para: "pgsql-general" <pgsql-general@lists.postgresql.org>
Enviadas: Segunda-feira, 14 de setembro de 2020 13:10:23
Assunto: Re: Effective IO Concurrency

On 9/14/20 11:03 AM, Laurenz Albe wrote:

On Mon, 2020-09-14 at 10:39 -0300, luis.roberto@siscobra.com.br wrote:

In PostgreSQL 13, the way of using effective_io_concurrency has changed. Until v12,
I used 200 for this value (using SSD drives). Using the new formula described in
https://www.postgresql.org/docs/13/release-13.html gives me 1176.
However, in the documentation https://www.postgresql.org/docs/13/runtime-config-resource.html#GUC-EFFECTIVE-IO-CONCURRENCY
it says that the maximum value allowed is 1000.

Then use the value 1000...

I think he means that the formula should take that into account.

--
Angular momentum makes the world go 'round.

Exactly....

For future reference, and maybe a updated documentation:

SELECT least(round(sum(OLD / n::float)),1000) FROM generate_series(1, OLD) s(n)

I don't know how to write patches, so maybe someone can do that.

Thanks.