effective_io_concurrency and NVMe devices - Mailing list pgsql-hackers

From Bruce Momjian
Subject effective_io_concurrency and NVMe devices
Date
Msg-id Yl92RVoXVfs+z2Yj@momjian.us
Whole thread Raw
Responses Re: effective_io_concurrency and NVMe devices  (Nathan Bossart <nathandbossart@gmail.com>)
Re: effective_io_concurrency and NVMe devices  (David Rowley <dgrowleyml@gmail.com>)
List pgsql-hackers
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.)

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Indecision is a decision.  Inaction is an action.  Mark Batterson




pgsql-hackers by date:

Previous
From: "wangw.fnst@fujitsu.com"
Date:
Subject: RE: Logical replication timeout problem
Next
From: Amit Kapila
Date:
Subject: Re: typos