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 4B738D1B1A1 for ; Fri, 11 Jun 2004 11:40:13 -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 52277-05 for ; Fri, 11 Jun 2004 14:40:08 +0000 (GMT) Received: from mail.astudios.com (unknown [66.49.77.3]) by svr1.postgresql.org (Postfix) with ESMTP id 9024BD1B169 for ; Fri, 11 Jun 2004 11:39:59 -0300 (ADT) thread-index: AcRPwplQC8MaU931TJOaNVqM6SmWlA== Received: from [10.4.2.252] ([66.194.26.150]) by mail.astudios.com with Microsoft SMTPSVC(6.0.3790.0); Fri, 11 Jun 2004 10:44:28 -0400 Message-ID: <40C9C43F.2060402@sermonaudio.com> Content-Class: urn:content-classes:message Importance: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.132 Date: Fri, 11 Jun 2004 10:39:59 -0400 From: "Chris Hoover" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Domenico Sgarbossa" Cc: Subject: Re: Problems with vacuum! References: <003901c44fbb$a6f02090$70c8007e@xtecnica.it> In-Reply-To: <003901c44fbb$a6f02090$70c8007e@xtecnica.it> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 11 Jun 2004 14:44:28.0421 (UTC) FILETIME=[991BEB50:01C44FC2] X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200406/126 X-Sequence-Number: 7184 Domenico Sgarbossa wrote: > I'm running postgrSQL 7.2 on a linux Red Hat 8.0 box with 2GB of RAM > When I boot-up the system , this is the TOP situation: > > 11:59am up 4 min, 1 user, load average: 0.37, 0.26, 0.11 > > 77 processes: 74 sleeping, 3 running, 0 zombie, 0 stopped > > CPU states: 0.3% user, 0.7% system, 0.0% nice, 98.8% idle > > Mem: 1031020K av, 177808K used, 853212K free, 0K shrd, > 14744K buff > > Swap: 2096472K av, 0K used, 2096472K free > 67828K cached > > After I've done a vacuum , the situation is: > > > > 12:04pm up 8 min, 1 user, load average: 0.22, 0.23, 0.12 > > 78 processes: 76 sleeping, 2 running, 0 zombie, 0 stopped > > CPU states: 2.5% user, 1.9% system, 0.0% nice, 95.4% idle > > Mem: 1031020K av, 1016580K used, 14440K free, 0K shrd, > 18624K buff > > Swap: 2096472K av, 0K used, 2096472K free > 833896K cached > > As you see the memory used by vacuum isn't released anymore? Anyone > know why? > > My statement is: vacuumdb --analyze dbname > My pg paramaters on postgresql.conf are: > > # > # Shared Memory Size > # > shared_buffers = 2048 # 2*max_connections, min 16 > max_fsm_relations = 100 # min 10, fsm is free space map > max_fsm_pages = 10000 # min 1000, fsm is free space map > max_locks_per_transaction = 64 # min 10 > wal_buffers = 8 # min 4 > > # > # Non-shared Memory Sizes > # > sort_mem = 512 # min 32 > vacuum_mem = 8192 # min 1024 > Did anyone know why this happend? > > Distinti Saluti > > Sgarbossa Domenico > X Tecnica S.R.L. > www.xtecnica.com > Tel: 049/9409154 - 049/5970297 > Fax: 049/9400288 Your vacuum memory was released. However, the linux kernel likes to keep most memory in the cached buffer instead of totally freeing it. The guru's behind the kernel figured out they get better performance this way. HTH, Chris