Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Migration study, step 1: bulk write performance
- From: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>
- To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: Ron <rjpeace(at)earthlink(dot)net>, Mikael Carneholm <Mikael(dot)Carneholm(at)WirelessCar(dot)com>, pgsql-performance(at)postgresql(dot)org
- Subject: Re: Migration study, step 1: bulk write performance
- Date: Tue, 21 Mar 2006 16:23:14 -0600
On Tue, 2006-03-21 at 15:56, Tom Lane wrote: > Scott Marlowe <smarlowe(at)g2switchworks(dot)com> writes: > > I've also found that modest increases in commit_siblings and > > commit_delay help a lot on certain types of imports. > > On a data import? Those really should have zero effect on a > single-process workload. Or are you doing multiple concurrent imports? That, and it's a machine that's doing other things. Also, a lot of the imports are NOT bundled up into groups of transactions. i.e. lots and lots of individual insert queries.
- References:
- Migration study, step 1: bulk write performance optimization
- From: Mikael Carneholm
- Re: Migration study, step 1: bulk write performance
- From: Simon Riggs
- Re: Migration study, step 1: bulk write performance
- From: Ron
- Re: Migration study, step 1: bulk write performance
- From: Scott Marlowe
- Re: Migration study, step 1: bulk write performance
- From: Tom Lane
- Migration study, step 1: bulk write performance optimization
- Prev by Date: Re: Migration study, step 1: bulk write performance
- Next by Date: Poor performance o
- Previous by thread: Re: Migration study, step 1: bulk write performance
- Next by thread: Re: Migration study, step 1: bulk write performance
- Indexes: