X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id F37ADD1B538 for ; Thu, 23 Oct 2003 20:53:35 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 35736-02 for ; Thu, 23 Oct 2003 17:53:07 -0300 (ADT) Received: from lorax.kcilink.com (lorax.kciLink.com [206.112.95.1]) by svr1.postgresql.org (Postfix) with ESMTP id 3EDF5D1B511 for ; Thu, 23 Oct 2003 17:53:05 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by lorax.kcilink.com (Postfix) with ESMTP id D40CA3E34 for ; Thu, 23 Oct 2003 16:53:06 -0400 (EDT) Received: from lorax.kcilink.com ([127.0.0.1]) by localhost (lorax.kcilink.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 42288-03 for ; Thu, 23 Oct 2003 16:53:06 -0400 (EDT) Received: from lorax.kciLink.com (localhost [127.0.0.1]) by lorax.kcilink.com (Postfix) with ESMTP id 4BF343E2D for ; Thu, 23 Oct 2003 16:53:06 -0400 (EDT) Received: (from news@localhost) by lorax.kciLink.com (8.12.8p1/8.12.8/Submit) id h9NKr6EO015939 for pgsql-performance@postgresql.org; Thu, 23 Oct 2003 16:53:06 -0400 (EDT) To: pgsql-performance@postgresql.org Path: not-for-mail From: Vivek Khera Newsgroups: ml.postgres.performance Subject: Re: vacuum locking Date: Thu, 23 Oct 2003 16:53:05 -0400 Organization: Khera Communications, Inc., Rockville, MD Lines: 37 Message-ID: References: <16272.318.870000.93584@gargle.gargle.HOWL> <3F9006BF.40906@persistent.co.in> <16272.4154.489000.227676@gargle.gargle.HOWL> <200310170936.25997.josh@agliodbs.com> <16272.32044.80671.948532@jump.bivio.com> <16279.4988.496000.539525@gargle.gargle.HOWL> NNTP-Posting-Host: yertle.kcilink.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: lorax.kcilink.com 1066942386 45861 216.194.193.105 (23 Oct 2003 20:53:06 GMT) X-Complaints-To: daemon@kciLink.com NNTP-Posting-Date: Thu, 23 Oct 2003 20:53:06 +0000 (UTC) User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Portable Code, berkeley-unix) Cancel-Lock: sha1:btiQIYMSsvu14LH6dWGA7eJ3EwM= X-Virus-Scanned: by amavisd-new at kciLink.com X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/608 X-Sequence-Number: 4356 >>>>> "RN" == Rob Nagler writes: RN> Vivek Khera writes: >> AMI or Adaptec based? RN> Adaptec, I think. AIC-7899 LVD SCSI is what dmidecode says, and RN> Red Hat/Adaptec aacraid driver, Aug 18 2003 is what comes up when it Cool. No need to diddle with it, then. The Adaptec work quite well, especially if you have battery backup. Anyhow, it seems that as Tom mentioned, you are going into swap when your vacuum runs, so I'll suspect you're just at the edge of total memory utilization, and then you go over the top. Another theory is that the disk capacity is near saturation, the vacuum causes it to slow down just a smidge, and then your application opens additional connections to handle the incoming requests which don't complete fast enough, causing more memory usage with the additional postmasters created. Again, you suffer the slow spiral of death due to resource shortage. I'd start by getting full diagnosis of overall what your system is doing during the vacuum (eg, additional processes created) then see if adding RAM will help. Also, how close are you to the capacity of your disk bandwidth? I don't see that in your numbers. I know in freebsd I can run "systat -vmstat" and it gives me a percentage of utilization that lets me know when I'm near the capacity. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-240-453-8497 AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/