pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Merlin Moncure <mmoncure@gmail.com>
To: Carlo Stonebanks <stonec.register@sympatico.ca>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performace Optimization for Dummies
Date: Thu, 28 Sep 2006 13:17:53 -0400
Message-ID: <b42b73150609281017m7f8f9d86xfa32d38cec954af7@mail.gmail.com> (raw)
In-Reply-To: <efgu4v$276m$1@news.hub.org>
References: <efgu4v$276m$1@news.hub.org>

On 9/28/06, Carlo Stonebanks <stonec.register@sympatico.ca> wrote:
> We urgently need a major performance improvement. We are running the
> PostgreSQL 8.1.4 on a Windows 2003 x64 Server on a dual processor, dual core
> 3.2Ghz Xeon box with 4gb RAM and a RAID (sorry, I don't know what type) disc
> subsystem. Sorry about the long intro, but here are my questions:

are you using the 'copy' interface?

> 1) Are we paying any big penalties by running Windows vs LINUX (or any other
> OS)?

thats a tough question.  my gut says that windows will not scale as
well as recent linux kernels in high load environments.

> 2) Has the debate over PostgreSQL and Xeon processors been settled? Is this
> a factor?

hearing good things about the woodcrest. pre-woodcrest xeon (dempsey
down) is outclassed by the opteron.

> Below, please find what I believe are the configuration settings of interest
> in our system

1. can probably run fsync=off during the import
2. if import is single proecess, consider temporary bump to memory for
index creation. or, since you have four cores consider having four
processes import the data somehow.
3. turn off stats collector, stats_command_string, stats_row_level,
and autovacuum during import.

merlin

> Any help and advice will be much appreciated. TIA,
>
> Carlo
>
> max_connections = 100
> shared_buffers = 50000
> work_mem = 32768
> maintenance_work_mem = 32768
> checkpoint_segments = 128
> effective_cache_size = 10000
> random_page_cost = 3
> stats_start_collector = on
> stats_command_string = on
> stats_row_level = on
> autovacuum = on
>
>
>
>
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
>        subscribe-nomail command to majordomo@postgresql.org so that your
>        message can get through to the mailing list cleanly
>



view thread (40+ messages)  latest in thread

Message-ID: <b42b73150609281017m7f8f9d86xfa32d38cec954af7@mail.gmail.com>
Permalink:  ../b42b73150609281017m7f8f9d86xfa32d38cec954af7@mail.gmail.com/
Also on:    postgresql.org/message-id/b42b73150609281017m7f8f9d86xfa32d38cec954af7@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: mmoncure@gmail.com, stonec.register@sympatico.ca
  Subject: Re: Performace Optimization for Dummies
  In-Reply-To: <b42b73150609281017m7f8f9d86xfa32d38cec954af7@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox