Re: Gigantic load average spikes

2019-04-01 Thread Rene Romero Benavides
On Mon, Apr 1, 2019 at 10:35 AM rihad wrote: > On 04/01/2019 08:30 PM, Michel Pelletier wrote: > > > > On Sun, Mar 31, 2019 at 10:49 PM David Rowley < > david.row...@2ndquadrant.com> wrote: > >> >> Perhaps a bunch of processes waiting on the access exclusive lock on >> the materialized view being

Re: Gigantic load average spikes

2019-04-01 Thread rihad
On 04/01/2019 08:30 PM, Michel Pelletier wrote: On Sun, Mar 31, 2019 at 10:49 PM David Rowley mailto:david.row...@2ndquadrant.com>> wrote: Perhaps a bunch of processes waiting on the access exclusive lock on the materialized view being released? log_lock_waits might help you i

Re: Gigantic load average spikes

2019-04-01 Thread Michel Pelletier
On Sun, Mar 31, 2019 at 10:49 PM David Rowley wrote: > > Perhaps a bunch of processes waiting on the access exclusive lock on > the materialized view being released? > > log_lock_waits might help you if the MV takes more than a second to > refresh, otherwise, you might need to have a look at ungr

Re: Gigantic load average spikes

2019-04-01 Thread Adrian Klaver
On 4/1/19 8:06 AM, rihad wrote: On 04/01/2019 06:17 PM, Adrian Klaver wrote: On 3/31/19 10:08 PM, rihad wrote: What exactly do you mean by "running processes"? I don't think I've ever seen a Unix with only 1 to 3 running processes in total, so you are probably referring to processes in a certa

Re: Gigantic load average spikes

2019-04-01 Thread rihad
On 04/01/2019 06:17 PM, Adrian Klaver wrote: On 3/31/19 10:08 PM, rihad wrote: What exactly do you mean by "running processes"? I don't think I've ever seen a Unix with only 1 to 3 running processes in total, so you are probably referring to processes in a certain state. Runnable (R)? Uninterru

Re: Gigantic load average spikes

2019-04-01 Thread Adrian Klaver
On 3/31/19 10:08 PM, rihad wrote: What exactly do you mean by "running processes"? I don't think I've ever seen a Unix with only 1 to 3 running processes in total, so you are probably referring to processes in a certain state. Runnable (R)? Uninterruptible sleep (D)? Both? Something else? Just

Re: Gigantic load average spikes

2019-03-31 Thread David Rowley
On Mon, 1 Apr 2019 at 18:08, rihad wrote: > > > What exactly do you mean by "running processes"? I don't think I've ever > > seen a Unix with only 1 to 3 running processes in total, so you are > > probably referring to processes in a certain state. Runnable (R)? > > Uninterruptible sleep (D)? Both

Re: Gigantic load average spikes

2019-03-31 Thread rihad
What exactly do you mean by "running processes"? I don't think I've ever seen a Unix with only 1 to 3 running processes in total, so you are probably referring to processes in a certain state. Runnable (R)? Uninterruptible sleep (D)? Both? Something else? Just that, 250-300 running processes in

Re: Gigantic load average spikes

2019-03-31 Thread Peter J. Holzer
On 2019-03-31 19:23:11 +0400, rihad wrote: > Postgres 10.3 On freebsd 10.3 is almost idle, disk i/o about 5-10%, number > running processes about 1-3, cpu about 90% idle, then we run a i/o heavy job > like "refresh materialized view", cpu & disk i/o still not maxed out, all of > a sudden the number

Re: Gigantic load average spikes

2019-03-31 Thread Adrian Klaver
On 3/31/19 8:23 AM, rihad wrote: Postgres 10.3 On freebsd 10.3 is almost idle, disk i/o about 5-10%, number running processes about 1-3, cpu about 90% idle, then we run a i/o heavy job like "refresh materialized view", cpu & disk i/o still not maxed out, all of a sudden the number of running pr

Gigantic load average spikes

2019-03-31 Thread rihad
Postgres 10.3 On freebsd 10.3 is almost idle, disk i/o about 5-10%, number running processes about 1-3, cpu about 90% idle, then we run a i/o heavy job like "refresh materialized view", cpu & disk i/o still not maxed out, all of a sudden the number of running processes increases to about 250-30