On Fri, 11 Oct 2019 at 12:10, Kevin Fenzi <kevin(a)scrye.com> wrote:
On Fri, Oct 11, 2019 at 09:52:20AM -0400, Stephen John Smoogen wrote:
> Currently the load on db-koji is 140+ and it is slow and
> non-responsive to users. I believe it is the below change which has
> affected this. I would like to lower down io to 32 to see if that
> affects things and tune further if needed. I am not doing this until
> Kevin or Patrick are around as it will affect koji and there is an
> order needed
>
> diff --git a/roles/postgresql_server/templates/postgresql.conf
> b/roles/postgresql_server/templates/postgresql.conf
> index cbaaaae..341340c 100644
> --- a/roles/postgresql_server/templates/postgresql.conf
> +++ b/roles/postgresql_server/templates/postgresql.conf
> @@ -504,4 +504,4 @@ default_text_search_config = 'pg_catalog.english'
> #custom_variable_classes = '' # list of custom variable class
names
> #
> # Number of concurrent i/o operations at the same time. The default is 1.
> -effective_io_concurrency = 100
> +effective_io_concurrency = 32
We could try it, but I am not sure that would do the trick.
It was doing this before I had that value set...
The issue started around the time we upgraded to 1.18.0 koji, and also
added memory, so it's hard to know what change really caused it.
I guess we can try it, but I'd like to investgate some more today and
see if I can figure out a reason for this.
I did kill the existing dump.
I'm trying a different dump setting to see if it cause anything.
I am going to say cancel this FBR until other methods have been exhausted.
--
Stephen J Smoogen.