pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Steve Poe <spoe@sfnet.cc>
To: Nurlan Mukhanov (AL/EKZ) <Nurlan.Mukhanov@ericsson.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgresql works too slow
Date: Sun, 17 Apr 2005 22:42:21 -0700
Message-ID: <426348BD.3040002@sfnet.cc> (raw)
In-Reply-To: <70E6659A9338D8418379B4EC0CA5819137928D@erumomw002.eemea.ericsson.se>
References: <70E6659A9338D8418379B4EC0CA5819137928D@erumomw002.eemea.ericsson.se>

Nurlan,

Try enabliing your checkpoint_segments. In my example, our database 
restore took 75mins. After enabling checkpoints_segments to 20, we cut 
it down to less than 30 minutes.  Is your pg_xlog on a seperate disc..or 
at least a partition? This will help too. A checkpoints_segments of 20, 
if memory serves correctly, will occupy around 800-900M of disc space in 
pg_xlog.

Steve Poe


Nurlan Mukhanov (AL/EKZ) wrote:

>Hello. 
>
>I'm trying to restore my database from dump in several parrallel processes, but restore process works too slow.
>Number of rows about 100 000 000,
>RAM: 8192M
>CPU: Ultra Sparc 3
>Number of CPU: 4
>OS: SunOS sun 5.8
>RDBMS: PostgreSQL 8.0
>
>====================            prstat info            ====================
>
>   PID USERNAME  SIZE   RSS STATE  PRI NICE      TIME  CPU PROCESS/NLWP
> 14231 postgres   41M   37M sleep   58    0   0:00.01 0.2% postgres/1
> 14136 postgres   41M   37M sleep   58    0   0:00.03 0.2% postgres/1
> 14211 postgres   41M   37M sleep   58    0   0:00.01 0.2% postgres/1
> 14270 postgres   41M   37M sleep   58    0   0:00.00 0.2% postgres/1
> 13767 postgres   41M   37M sleep   58    0   0:00.18 0.2% postgres/1
> 13684 postgres   41M   36M sleep   58    0   0:00.14 0.2% postgres/1
>
> NPROC USERNAME  SIZE   RSS MEMORY      TIME  CPU
>    74 root      272M  191M   2.3%   0:26.29  24%
>   124 postgres 1520M 1306M    16%   0:03.05 5.0%
>
>
>How to encrease postgresql speed? Why postgres took only 5.0% of CPU time?
>
>Nurlan Mukhanov 
>
>---------------------------(end of broadcast)---------------------------
>TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>
>  
>




view thread (6+ messages)  latest in thread

Message-ID: <426348BD.3040002@sfnet.cc>
Permalink:  ../426348BD.3040002@sfnet.cc/
Also on:    postgresql.org/message-id/426348BD.3040002@sfnet.cc

 · 

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: spoe@sfnet.cc, Nurlan.Mukhanov@ericsson.com
  Subject: Re: Postgresql works too slow
  In-Reply-To: <426348BD.3040002@sfnet.cc>

* 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