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 A606D3A4430 for ; Wed, 19 Jan 2005 19:02:11 +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 41176-04 for ; Wed, 19 Jan 2005 19:02:04 +0000 (GMT) Received: from bayswater1.ymogen.net (unknown [217.27.247.154]) by svr1.postgresql.org (Postfix) with ESMTP id AE1E93A4476 for ; Wed, 19 Jan 2005 19:01:51 +0000 (GMT) Received: from [82.68.132.234] (82-68-132-234.dsl.in-addr.zen.co.uk [82.68.132.234]) by bayswater1.ymogen.net (Postfix) with ESMTP id 95140B3217; Wed, 19 Jan 2005 19:01:48 +0000 (GMT) Message-ID: <41EEAE9C.7070806@ymogen.net> Date: Wed, 19 Jan 2005 19:01:48 +0000 From: Matt Clark User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kevin Schroeder Cc: pgsql-performance@postgresql.org Subject: Re: Swapping on Solaris References: <042a01c4fdaf$fbb3b860$0200a8c0@WORKSTATION> <41EE0F05.9080901@coretech.co.nz> <41EE65FC.2000909@rentec.com> <00d601c4fe33$89682eb0$0200a8c0@WORKSTATION> <41EE7D19.4060503@rentec.com> <014801c4fe3d$2a2478f0$0200a8c0@WORKSTATION> <41EE9315.2010707@rentec.com> <019701c4fe49$8c72d4a0$0200a8c0@WORKSTATION> In-Reply-To: <019701c4fe49$8c72d4a0$0200a8c0@WORKSTATION> Content-Type: text/plain; charset=ISO-8859-1; 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/248 X-Sequence-Number: 9938 This page may be of use: http://www.serverworldmagazine.com/monthly/2003/02/solaris.shtml From personal experience, for god's sake don't think Solaris' VM/swap implementation is easy - it's damn good, but it ain't easy! Matt Kevin Schroeder wrote: > I think it's probably just reserving them. I can't think of anything > else. Also, when I run swap activity with sar I don't see any > activity, which also points to reserved swap space, not used swap space. > > swap -s reports > > total: 358336k bytes allocated + 181144k reserved = 539480k used, > 2988840k available > > Kevin > > ----- Original Message ----- From: "Alan Stange" > To: "Kevin Schroeder" > Cc: > Sent: Wednesday, January 19, 2005 11:04 AM > Subject: Re: [PERFORM] Swapping on Solaris > > >> Kevin Schroeder wrote: >> >>> I may be asking the question the wrong way, but when I start up >>> PostgreSQL swap is what gets used the most of. I've got 1282MB free >>> RAM right now and and 515MB swap in use. Granted, swap file usage >>> probably wouldn't be zero, but I would guess that it should be a lot >>> lower so something must be keeping PostgreSQL from using the free >>> RAM that my system is reporting. For example, one of my postgres >>> processes is 201M in size but on 72M is resident in RAM. That extra >>> 130M is available in RAM, according to top, but postgres isn't using >>> it. >> >> >> The test you're doing doesn't measure what you think you're measuring. >> >> First, what else is running on the machine? Note that some shared >> memory allocations do reserve backing pages in swap, even though the >> pages aren't currently in use. Perhaps this is what you're >> measuring? "swap -s" has better numbers than top. >> >> You'd be better by trying a reboot then starting pgsql and seeing >> what memory is used. >> >> Just because you start a process and see the swap number increase >> doesn't mean that the new process is in swap. It means some >> anonymous pages had to be evicted to swap to make room for the new >> process or some pages had to be reserved in swap for future use. >> Typically a new process won't be paged out unless something else is >> causing enormous memory pressure... >> >> -- Alan >> >> >> > > > ---------------------------(end of broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly