| From: | Christopher Opena <counterveil(at)gmail(dot)com> |
|---|---|
| To: | Alan Hodgson <ahodgson(at)simkin(dot)ca> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Puzzling full database lock |
| Date: | 2012-02-02 05:56:16 |
| Message-ID: | CAFOrgqfZTC+BQ_zXMLV6NvkwEiLp7Qf2PGx98XjZijbHsiqLbg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Yeah, it's strange because we definitely have periods of high iowait but
this is not when the locks are happening. If I could correlate it directly
to that it would be so much easier. Thanks again for the response!
On Wed, Feb 1, 2012 at 8:42 PM, Alan Hodgson <ahodgson(at)simkin(dot)ca> wrote:
> On Wednesday, February 01, 2012 05:13:15 PM Christopher Opena wrote:
> > Do you mean 6-12% of total iowait, or per cpu? Our average iowait in the
> > last week is 34.31% of a total 1600% with an average idle of 1451.76%.
> Our
> > iowait *does* spike occasionally (today it went up to 148.01%) but it
> > doesn't coincide with the lock happening. At the time of the lock we
> were
> > at 10.58% iowait, which is quite a bit below our average.
> >
>
> Total, but it doesn't sound like that's the problem.
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dennis | 2012-02-02 06:09:08 | What is the best way to force character data to upper case |
| Previous Message | Alan Hodgson | 2012-02-02 04:42:37 | Re: Puzzling full database lock |