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 503613A427D for ; Wed, 19 Jan 2005 15:09:20 +0000 (GMT) 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 97095-10 for ; Wed, 19 Jan 2005 15:09:02 +0000 (GMT) Received: from COLSWEEPER.cranel.com (newmail.cranel.com [66.192.200.227]) by svr1.postgresql.org (Postfix) with ESMTP id BF8333A4169 for ; Wed, 19 Jan 2005 15:09:01 +0000 (GMT) Received: from colmail01.cranel.local (colmail01.cranel.local) by COLSWEEPER.cranel.com (Content Technologies SMTPRS 4.3.14) with ESMTP id ; Wed, 19 Jan 2005 10:06:52 -0500 Received: from [192.168.11.134] (192.168.11.134 [192.168.11.134]) by colmail01.cranel.local with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id DD74VHV4; Wed, 19 Jan 2005 10:08:11 -0500 Message-ID: <41EE77C1.1010900@cranel.com> Date: Wed, 19 Jan 2005 10:07:45 -0500 From: Greg Spiegelberg Organization: Cranel, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913 X-Accept-Language: en-us, en MIME-Version: 1.0 To: stange@rentec.com Cc: Kevin Schroeder , pgsql-performance@postgresql.org Subject: Re: Swapping on Solaris References: <042a01c4fdaf$fbb3b860$0200a8c0@WORKSTATION> <41EE0F05.9080901@coretech.co.nz> <41EE65FC.2000909@rentec.com> In-Reply-To: <41EE65FC.2000909@rentec.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200501/239 X-Sequence-Number: 9929 Alan Stange wrote: > > Note that files in /tmp are usually in a tmpfs file system. These > files may be the usage of swap that you're seeing (as they will be paged > out on an active system with some memory pressure) You can do a couple things with /tmp. Create a separate file system for it so it will have zero impact on swap and use the "noatime" mount option. Alternatively, limit the size of /tmp using the mount option "size=MBm" replacing "MB" with the size you want it to be in MBytes. If your application uses /tmp heavily, be sure to put it on a speedy, local LUN. > Finally, just as everyone suggests upgrading to newer postgresql > releases, you probably want to get to a newer Solaris release. If you really want to avoid swapping I'd suggest tuning your database first with swap turned off and put it under a "normal" load while watching both top and vmstat. When you're happy with it, turn swap back on for those "heavy" load times and move on. Greg -- Greg Spiegelberg Product Development Manager Cranel, Incorporated. Phone: 614.318.4314 Fax: 614.431.8388 Email: gspiegelberg@cranel.com Technology. Integrity. Focus.