| From: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: hint in determining effective_io_concurrency |
| Date: | 2021-04-22 20:22:59 |
| Message-ID: | CAKoxK+7XVNxR_ttj-uOE9Pkw9=fEXX8LSJ5OVLi90RA+oc_X5A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, Apr 22, 2021 at 10:15 PM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> Note that the interpretation of this GUC changed in v13.
> https://www.postgresql.org/docs/13/release-13.html
> |Change the way non-default effective_io_concurrency values affect concurrency (Thomas Munro)
> |Previously, this value was adjusted before setting the number of concurrent requests. The value is now used directly. Conversion of old values to new ones can be done using:
> |SELECT round(sum(OLDVALUE / n::float)) AS newvalue FROM generate_series(1, OLDVALUE) s(n);
>
Yeah, I know, thanks.
However, I'm still curious about which tools to use to get info about
the storage queue/concurrency.
Luca
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2021-04-22 20:27:39 | Re: hint in determining effective_io_concurrency |
| Previous Message | Justin Pryzby | 2021-04-22 20:15:06 | Re: hint in determining effective_io_concurrency |