No subject

Unknown Unknown
Sun Mar 21 11:54:51 PDT 2010

el at>    <201003202324.o2KNOrlX006114 at> <1427. at>
From: Chris Turner <c.turner at>
Subject: Re: Machine unresponsive with cache_lock: blocked on... message
Date: Sun, 21 Mar 2010 18:56:26 +0000
List-Post: <mailto:bugs at>
List-Subscribe: <mailto:bugs-request at>
List-Unsubscribe: <mailto:bugs-request at>
List-Help: <mailto:bugs-request at>
List-Owner: <mailto:owner-bugs at>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
In-Reply-To: <1427. at>
Sender: bugs-errors at
Errors-To: bugs-errors at
Lines: 21
X-Trace: 1269197759 55376
Xref: dragonfly.bugs:11550

elekktretterr at wrote:
> question: why is HAMMER using so much memory, causing applications like
> postgres to use swap (and thus run slow).

this response isn't at all hammer related.. but in any case:

Still a bit fuzzy on some the related issues that might be at play here, 
but as I understand it, the postgres data cache uses as much shared 
memory as it 'wants' (e.g. up to max configured) to hold the database 
data - so if this machine was up for a long time, potentially the entire 
database data set is in memory -

and if the data set isn't used very often, it might get swapped out by 
something else running or just from inactivity ..

If you want to keep this from happening, you can set:


in /boot/loader.conf

More information about the Bugs mailing list