From: | "Anjan Dave" <adave(at)vantage(dot)com> |
---|---|
To: | "Matt Clark" <matt(at)ymogen(dot)net> |
Cc: | "Rod Taylor" <pg(at)rbt(dot)ca>, "Postgresql Performance" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: can't handle large number of INSERT/UPDATEs |
Date: | 2004-10-26 21:15:49 |
Message-ID: | 4BAFBB6B9CC46F41B2AD7D9F4BBAF7850985DE@vt-pe2550-001.vantage.vantage.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
That is 1 or maybe 2 second interval.
One thing I am not sure is why 'bi' (disk writes) stays at 0 mostly,
it's the 'bo' column that shows high numbers (reads from disk). With so
many INSERT/UPDATEs, I would expect it the other way around...
-anjan
-----Original Message-----
From: Matt Clark [mailto:matt(at)ymogen(dot)net]
Sent: Tuesday, October 26, 2004 2:29 PM
To: Anjan Dave
Cc: Rod Taylor; Postgresql Performance
Subject: Re: [PERFORM] can't handle large number of INSERT/UPDATEs
>I don't have iostat on that machine, but vmstat shows a lot of writes
to
>the drives, and the runnable processes are more than 1:
>
> 6 1 0 3617652 292936 2791928 0 0 0 52430 1347 4681 25
>19 20 37
>
>
Assuming that's the output of 'vmstat 1' and not some other delay,
50MB/second of sustained writes is usually considered 'a lot'.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-10-26 21:53:14 | Re: can't handle large number of INSERT/UPDATEs |
Previous Message | Anjan Dave | 2004-10-26 21:13:04 | Re: can't handle large number of INSERT/UPDATEs |