| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Clodoaldo <clodoaldo(dot)pinto(dot)neto(at)gmail(dot)com> |
| Cc: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>, "PostgreSQL - General ML" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: ATTN: Clodaldo was Performance problem. Could it be related to 8.3-beta4? |
| Date: | 2008-01-16 04:39:38 |
| Message-ID: | 17789.1200458378@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I went through this thread again, and noticed something that no one
seems to have remarked on at the time: the vmstat numbers near the
bottom of this post
http://archives.postgresql.org/pgsql-general/2008-01/msg00161.php
show close to 100% I/O wait time (either that or 50% idle 50% I/O wait,
which I suspect is an artifact). We subsequently concluded that the
"SELECT" side of the INSERT/SELECT command is not where the problem is,
so all the cycles are going into the actual row insertion part.
I don't know of any reason to think that insertion is slower in 8.3
than it was in 8.2, and no one else has reported anything of the sort.
So I'm leaning to the idea that this suggests some kind of
misconfiguration of the disk setup in Clodoaldo's new server. There
was some earlier discussion about not having the RAID configured right:
http://archives.postgresql.org/pgsql-general/2008-01/msg00169.php
I'm thinking it's still not right :-( but have no real expertise
at diagnosing such problems. Anyone?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Treat | 2008-01-16 04:53:05 | Re: advocacy: drupal and PostgreSQL |
| Previous Message | Tom Lane | 2008-01-16 03:46:13 | Re: Segmentation fault with 8.3 FTS ISpell |