|
Home > Archive > PostgreSQL Performance > March 2006 > Re: Migration study, step 1: bulk write performance
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: Migration study, step 1: bulk write performance
|
|
| Scott Marlowe 2006-03-21, 8:33 pm |
| On Mon, 2006-03-20 at 15:17, Ron wrote:
> At 03:44 PM 3/21/2006, Simon Riggs wrote:
> IIRC, Josh Berkus did some benches that suggests in pg 8.x a value of
> 64 - 256 is best for checkpoint_segments as long as you have the RAM available.
>
> I'd suggest trying values of 64, 128, and 256 and setting
> checkpoint_segments to the best of those.
I've also found that modest increases in commit_siblings and
commit_delay help a lot on certain types of imports.
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
| |
| Tom Lane 2006-03-21, 8:33 pm |
| Scott Marlowe < smarlowe@g2switchwor
ks.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?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
|
|
|
|
|