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 9224C3A3F06 for ; Wed, 19 Jan 2005 15:17:07 +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 97837-08 for ; Wed, 19 Jan 2005 15:16:57 +0000 (GMT) Received: from mail.blogtap.com (66.241.8.26.maxuptime.com [66.241.8.26]) by svr1.postgresql.org (Postfix) with ESMTP id 5D32C3A4280 for ; Wed, 19 Jan 2005 15:16:57 +0000 (GMT) Received: from WORKSTATION (c-24-1-91-108.client.comcast.net [24.1.91.108]) by mail.blogtap.com (Postfix) with ESMTP id B8B7E68015 for ; Wed, 19 Jan 2005 09:14:55 -0600 (CST) Message-ID: <013301c4fe39$ee326e90$0200a8c0@WORKSTATION> From: "Kevin Schroeder" Cc: References: <042a01c4fdaf$fbb3b860$0200a8c0@WORKSTATION> <41EE0F05.9080901@coretech.co.nz> <41EE65FC.2000909@rentec.com> <41EE77C1.1010900@cranel.com> Subject: Re: Swapping on Solaris Date: Wed, 19 Jan 2005 09:17:03 -0600 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200501/237 X-Sequence-Number: 9927 /tmp doesn't seem to be much of a problem. I have about 1k worth of data in there and 72k in /var/tmp. Would turning swap off help in tuning the database in this regard? top is reporting that there's 1.25GB of RAM free on a 2GB system so, in my estimation, there's no need for PostgreSQL to be swapped unless that free memory is Solaris caching files in RAM. Kevin ----- Original Message ----- From: "Greg Spiegelberg" To: Cc: "Kevin Schroeder" ; Sent: Wednesday, January 19, 2005 9:07 AM Subject: Re: [PERFORM] Swapping on Solaris > 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. > > > >