X-Original-To: pgsql-performance@postgresql.org Received: from spampd.localdomain (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 1C993475A80 for ; Sun, 20 Apr 2003 14:36:20 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 42A4B47580B for ; Sun, 20 Apr 2003 14:36:19 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h3KIaAU6010083; Sun, 20 Apr 2003 14:36:10 -0400 (EDT) To: Ian Knopke Cc: pgsql-performance@postgresql.org Subject: Re: problems In-reply-to: References: Comments: In-reply-to Ian Knopke message dated "Sun, 20 Apr 2003 14:09:05 -0400" Date: Sun, 20 Apr 2003 14:36:10 -0400 Message-ID: <10082.1050863770@sss.pgh.pa.us> From: Tom Lane X-Spam-Status: No, hits=-32.5 required=5.0 tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, REFERENCES,REPLY_WITH_QUOTES autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) X-Archive-Number: 200304/183 X-Sequence-Number: 1689 Ian Knopke writes: > Comparing the beginning and end times from the log, it seems to take the > same amount of time to insert at the beginning of the process as after > about twenty minutes. However, I also logged the input from vmstat, which > shows the amount of memory available shrinking rapidly. AFAICT you are just showing us kernel disk cache expanding to fill unused memory. This is normal and not a cause for alarm. > Eventually the system moves to using swap and things really slow down. Disk cache can't cause swapping --- the kernel will just throw away cached pages when the memory is needed for something else. It could be that you have growth in the number of Postgres processes, or the sizes of individual processes, but vmstat isn't very helpful for determining that (good ol' top would be more useful). In any case you haven't actually shown us any data from the state where the system is slow, so it's a bit hard to conjecture about what's going on. Some other important information that you haven't let us in on is the platform and the Postgres version you're using. regards, tom lane