| 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 01:13:15 |
| Message-ID: | CAFOrgqeL98-WO8BSfz7rKWMkaGJASAwSVFavt+G5JomtmMuRcQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
Thanks,
-Chris.
On Wed, Feb 1, 2012 at 4:55 PM, Alan Hodgson <ahodgson(at)simkin(dot)ca> wrote:
>
>
> Define "low I/O". The only things I've ever seen interfere with console
> access
> are running out of memory or excessive disk i/o. If you're seeing even
> 6-12%
> iowait on a 16 core machine you might very well have swamped your available
> disk I/O.
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alan Hodgson | 2012-02-02 04:42:37 | Re: Puzzling full database lock |
| Previous Message | Ondrej Ivanič | 2012-02-02 01:12:17 | Re: Puzzling full database lock |