On Sun, 2007-12-16 at 16:11 -0800, Joshua D. Drake wrote:
> On Sun, 16 Dec 2007 17:55:55 -0600
> "Scott Marlowe" <[EMAIL PROTECTED]> wrote:
>
> > On Dec 14, 2007 1:33 AM, Ow Mun Heng <[EMAIL PROTECTED]> wrote:
> > > I kept looking at the io columns and didn't even think of the swap
> > > partitio
On Dec 16, 2007 6:11 PM, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Sun, 16 Dec 2007 17:55:55 -0600
> "Scott Marlowe" <[EMAIL PROTECTED]> wrote:
>
> > On Dec 14, 2007 1:33 AM, Ow Mun Heng <[EMAIL PROTECTED]> wrote:
> > > I kept looking at the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 16 Dec 2007 17:55:55 -0600
"Scott Marlowe" <[EMAIL PROTECTED]> wrote:
> On Dec 14, 2007 1:33 AM, Ow Mun Heng <[EMAIL PROTECTED]> wrote:
> > I kept looking at the io columns and didn't even think of the swap
> > partition. It's true that it's m
On Dec 14, 2007 1:33 AM, Ow Mun Heng <[EMAIL PROTECTED]> wrote:
> I kept looking at the io columns and didn't even think of the swap
> partition. It's true that it's moving quite erratically but I won't say
> that it's really thrashing.
>
> total used free sharedbuf
Ow Mun Heng <[EMAIL PROTECTED]> writes:
>> vmstat would confirm or disprove that particular guess, since it tracks
>> swap I/O separately.
> procs ---memory-- ---swap-- -io --system--
> -cpu--
> r b swpd free buff cache si sobibo in cs us s
On Fri, 2007-12-14 at 01:54 -0500, Tom Lane wrote:
> "Merlin Moncure" <[EMAIL PROTECTED]> writes:
> > there are a few things that I can think of that can can cause postgres
> > to cause i/o on a drive other than the data drive:
> > * logging (eliminate this by moving logs temporarily)
I'll have to
On Thu, 13 Dec 2007, Ow Mun Heng wrote:
I'm using centos 5 as the OS so, there's no fancy dtrace to look at
which processes is causing my disks to thrash.
Does plain old top show you anything interesting? If you hit 'c' after
starting it you'll get more information about the postgres process
"Merlin Moncure" <[EMAIL PROTECTED]> writes:
> there are a few things that I can think of that can can cause postgres
> to cause i/o on a drive other than the data drive:
> * logging (eliminate this by moving logs temporarily)
> * swapping (swap is high and changing, other ways)
> * dumps, copy sta
On Dec 13, 2007 6:06 AM, Ow Mun Heng <[EMAIL PROTECTED]> wrote:
> I'm using centos 5 as the OS so, there's no fancy dtrace to look at
> which processes is causing my disks to thrash.
>
> I have 4 disks in the box. (all ide, 7200rpm)
>
> 1 OS disk [hda]
> 2 raided (1) disks [hdb/hdc]
> 1 pg_xlog dis
On Dec 13, 2007 5:06 AM, Ow Mun Heng <[EMAIL PROTECTED]> wrote:
> I'm using centos 5 as the OS so, there's no fancy dtrace to look at
> which processes is causing my disks to thrash.
>
> I have 4 disks in the box. (all ide, 7200rpm)
>
> 1 OS disk [hda]
> 2 raided (1) disks [hdb/hdc]
> 1 pg_xlog dis
I'm using centos 5 as the OS so, there's no fancy dtrace to look at
which processes is causing my disks to thrash.
I have 4 disks in the box. (all ide, 7200rpm)
1 OS disk [hda]
2 raided (1) disks [hdb/hdc]
1 pg_xlog disk (and also used as an alternate tablespace for [hdd]
temp/in-transit files vi
11 matches
Mail list logo
