Horton

Re: effective_io_concurrency's steampunk spindle maths

eshishki <itparanoia@gmail.com>

View thread View on postgr.es
From: Evgeniy Shishkin <itparanoia@gmail.com>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Tomas Vondra <tomas.vondra@2ndquadrant.com>, Andres Freund <andres@anarazel.de>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2020-03-07T10:54:40Z
Lists: pgsql-hackers 

> On Mar 7, 2020, at 00:33, Thomas Munro <thomas.munro@gmail.com> wrote:
> 
> That is indeed what led me to start thinking about what a good new
> name would be.  

MySQL has a term io_capacity.
https://dev.mysql.com/doc/refman/8.0/en/innodb-configuring-io-capacity.html 
> The innodb_io_capacity variable defines the overall I/O capacity available to InnoDB. It should be set to approximately the number of I/O operations that the system can perform per second (IOPS). When innodb_io_capacity is set, InnoDB estimates the I/O bandwidth available for background tasks based on the set value.
> 

Perhaps we can have maintenance_io_capacity as well.

Commits

  1. Introduce a maintenance_io_concurrency setting.

  2. Simplify the effective_io_concurrency setting.