Re: effective_io_concurrency and NVMe devices - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: effective_io_concurrency and NVMe devices
Date
Msg-id 20220420175858.GA2634425@nathanxps13
Whole thread Raw
In response to effective_io_concurrency and NVMe devices  (Bruce Momjian <bruce@momjian.us>)
Responses RE: effective_io_concurrency and NVMe devices  (Jakub Wartak <Jakub.Wartak@tomtom.com>)
List pgsql-hackers
On Tue, Apr 19, 2022 at 10:56:05PM -0400, Bruce Momjian wrote:
> NVMe devices have a maximum queue length of 64k:
> 
>     https://blog.westerndigital.com/nvme-queues-explained/
> 
> but our effective_io_concurrency maximum is 1,000:
> 
>     test=> set effective_io_concurrency = 1001;
>     ERROR:  1001 is outside the valid range for parameter "effective_io_concurrency" (0 .. 1000)
> 
> Should we increase its maximum to 64k?  Backpatched?  (SATA has a
> maximum queue length of 256.)

If there are demonstrable improvements with higher values, this seems
reasonable to me.  I would even suggest removing the limit completely so
this doesn't need to be revisited in the future.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: [Proposal] vacuumdb --schema only
Next
From: Tomas Vondra
Date:
Subject: Re: Bad estimate with partial index