Re: can't handle large number of INSERT/UPDATEs
От | Anjan Dave |
---|---|
Тема | Re: can't handle large number of INSERT/UPDATEs |
Дата | |
Msg-id | 4BAFBB6B9CC46F41B2AD7D9F4BBAF7850985DE@vt-pe2550-001.vantage.vantage.com обсуждение исходный текст |
Ответ на | can't handle large number of INSERT/UPDATEs ("Anjan Dave" <adave@vantage.com>) |
Ответы |
Re: can't handle large number of INSERT/UPDATEs
|
Список | 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@ymogen.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'.
В списке pgsql-performance по дате отправления: