Re: hint in determining effective_io_concurrency
От | Merlin Moncure |
---|---|
Тема | Re: hint in determining effective_io_concurrency |
Дата | |
Msg-id | CAHyXU0wgwtY7KxjvZhCbfo7jk_L6xWfoB4tynAnnc2tJrjQzoQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: hint in determining effective_io_concurrency (Luca Ferrari <fluca1978@gmail.com>) |
Ответы |
Re: hint in determining effective_io_concurrency
|
Список | pgsql-performance |
On Thu, Apr 22, 2021 at 2:55 PM Luca Ferrari <fluca1978@gmail.com> wrote: > > On Thu, Apr 22, 2021 at 9:52 PM Bruce Momjian <bruce@momjian.us> wrote: > > > > On Thu, Apr 22, 2021 at 09:45:15PM +0200, Luca Ferrari wrote: > > > Hi all, > > > I'm unable to find (apparently) a way to find out a possible value to > > > start with for effective_io_concurrency. > > > I suspect that benchmarking, e.g., using bonnie++ or sysbench and > > > testing with different values of concurrency could help to determine > > > the max number of concurrent request, (tps, lower latency, ecc.). > > > Is thjs correct or is there another suggested way? > > > > I recommend 256 for SSDs or other RAM-like fsync systems, and maybe > > maybe 16 for magnetic. > > > Thanks Bruce, this is a very good starting point. > But is there a rationale about those numbers? I mean, if I change the > storage system, how should I set a correct number? See thread, https://postgrespro.com/list/thread-id/2069516 The setting only impacts certain scan operations, it's not a gamechanger. merlin
В списке pgsql-performance по дате отправления: