From: Kevin Schroeder <kschroeder@mirageworks.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Swapping on Solaris
Date: Wed, 19 Jan 2005 13:46:51 -0600
Message-ID: <022601c4fe5f$9f3f98f0$0200a8c0@WORKSTATION> (raw)
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>
<41EEAE9C.7070806@ymogen.net>
Well, easy it ain't and I believe it's good. One final question: When I
run sar -w I get no swap activity, but the process switch column registers
between 400 and 700 switches per second. Would that be in the normal range
for a medium-use system?
Thanks
Kevin
----- Original Message -----
From: "Matt Clark" <matt@ymogen.net>
To: "Kevin Schroeder" <kschroeder@mirageworks.com>
Cc: <pgsql-performance@postgresql.org>
Sent: Wednesday, January 19, 2005 1:01 PM
Subject: Re: [PERFORM] Swapping on Solaris
> 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" <stange@rentec.com>
>> To: "Kevin Schroeder" <kschroeder@mirageworks.com>
>> Cc: <pgsql-performance@postgresql.org>
>> 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
>
>
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: kschroeder@mirageworks.com
Subject: Re: Swapping on Solaris
In-Reply-To: <022601c4fe5f$9f3f98f0$0200a8c0@WORKSTATION>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox