X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id D179153986 for ; Mon, 18 Apr 2005 02:43:15 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 64737-06 for ; Mon, 18 Apr 2005 05:43:12 +0000 (GMT) Received: from mail.tecarta.com (66.238.115.135.ptr.us.xo.net [66.238.115.135]) by svr1.postgresql.org (Postfix) with ESMTP id 1E7BB53982 for ; Mon, 18 Apr 2005 02:43:09 -0300 (ADT) Received: from mail pickup service by mail.tecarta.com with Microsoft SMTPSVC; Sun, 17 Apr 2005 22:46:10 -0700 Received: from mail.tecarta.com ([192.168.160.2]) by mail.tecarta.com with Microsoft SMTPSVC(6.0.3790.0); Sun, 17 Apr 2005 22:46:06 -0700 Received: from barracuda.tecarta.com ([192.168.160.200]) by mail.tecarta.com (SAVSMTP 3.1.0.29) with SMTP id M2005041722460609075 for ; Sun, 17 Apr 2005 22:46:06 -0700 X-ASG-Debug-ID: 1113802982-23135-1-0 X-Barracuda-URL: http://192.168.160.200:8000/cgi-bin/mark.cgi Received: from mail1 (mail1.hq.corp [192.168.160.5]) by barracuda.tecarta.com (Spam Firewall) with SMTP id F1102200D56C for ; Sun, 17 Apr 2005 22:43:02 -0700 (PDT) Received: from [192.168.0.13] ([63.206.203.145]) by mail.tecarta.com with Microsoft SMTPSVC(6.0.3790.0); Sun, 17 Apr 2005 22:46:01 -0700 Message-ID: <426348BD.3040002@sfnet.cc> Date: Sun, 17 Apr 2005 22:42:21 -0700 From: Steve Poe User-Agent: Mozilla Thunderbird 1.0 (X11/20041228) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Nurlan Mukhanov (AL/EKZ)" Cc: pgsql-performance@postgresql.org X-ASG-Orig-Subj: Re: [PERFORM] Postgresql works too slow Subject: Re: Postgresql works too slow References: <70E6659A9338D8418379B4EC0CA5819137928D@erumomw002.eemea.ericsson.se> In-Reply-To: <70E6659A9338D8418379B4EC0CA5819137928D@erumomw002.eemea.ericsson.se> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 18 Apr 2005 05:46:01.0224 (UTC) FILETIME=[E6FD2080:01C543D9] X-Virus-Scanned: by Barracuda Spam Firewall at tecarta.com X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=4.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=7.0 tests=BAYES_50 X-Barracuda-Spam-Report: Code version 3.02, rules version 3.0.364 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.00 BAYES_50 BODY: Bayesian spam probability is 40 to 60% [score: 0.5021] X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.181 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200504/384 X-Sequence-Number: 11781 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 > > >