Re: can't handle large number of INSERT/UPDATEs - Mailing list pgsql-performance

From Anjan Dave
Subject Re: can't handle large number of INSERT/UPDATEs
Date
Msg-id 4BAFBB6B9CC46F41B2AD7D9F4BBAF7850985E1@vt-pe2550-001.vantage.vantage.com
Whole thread Raw
In response to can't handle large number of INSERT/UPDATEs  ("Anjan Dave" <adave@vantage.com>)
List pgsql-performance
Ok, i was thinking from the disk perspective. Thanks!

    -----Original Message----- 
    From: Tom Lane [mailto:tgl@sss.pgh.pa.us] 
    Sent: Tue 10/26/2004 6:37 PM 
    To: Anjan Dave 
    Cc: Matt Clark; Rod Taylor; Postgresql Performance 
    Subject: Re: [PERFORM] can't handle large number of INSERT/UPDATEs 
    
    

    "Anjan Dave" <adave@vantage.com> writes: 
    > 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... 

    Er ... it *is* the other way around.  bi is blocks in (to the CPU), 
    bo is blocks out (from the CPU). 

                            regards, tom lane 


pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: can't handle large number of INSERT/UPDATEs
Next
From: Curtis Zinzilieta
Date:
Subject: Re: can't handle large number of INSERT/UPDATEs