Search Postgresql Archives

Re: Performance large tables.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Benjamin Arai
wrote on Saturday, December 10, 2005 3:37 PM
> ... On the other hand there is a weekly update (This is the 
> problem) that updates all of the modified records for a bunch of 
> finacial data such as closes and etc.  For the most part they are 
> records of the type name,date,value.  The update currently takes almost 
> two days.   The update does deletions, insertion, and updates depending 
> on what has happened from the previous week.
> 
> For the most part the updates are simple one liners.  I currently commit 
> in large batch to increase performance but it still takes a while as 
> stated above.  From evaluating the computers performance during an 
> update,  the system is thrashing both memory and disk.  

I experimented with batch size and found that large batches (thousands or
tens of thousands) slowed things down in our situation, while using a 
batch size of around 100 or so sped things up tremendously. 
Of course, YMMV ...

-Roger


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux