From owner-freebsd-current@FreeBSD.ORG Thu Jun 12 00:22:03 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B4DD0799 for ; Thu, 12 Jun 2014 00:22:03 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3434E2902 for ; Thu, 12 Jun 2014 00:22:02 +0000 (UTC) Received: from mandree.no-ip.org ([78.49.235.180]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0LvyAz-1Wgc9812Sr-017iKe for ; Thu, 12 Jun 2014 02:21:55 +0200 Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id 8BD5923CEED for ; Thu, 12 Jun 2014 02:21:54 +0200 (CEST) Message-ID: <5398F2A2.2020808@gmx.de> Date: Thu, 12 Jun 2014 02:21:54 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: CURRENT: why is CURRENT swapping so fast? References: <20140612003612.25cc2851.ohartman@zedat.fu-berlin.de> In-Reply-To: <20140612003612.25cc2851.ohartman@zedat.fu-berlin.de> X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:oWTXPr7l857dKK3/2dGMAjZjf3xnXM0q/vrpvQ4ovZOhnWjMVlx H5p0IobOjw/Mhn/y3KsmSJHUEFZSj0244ktvuGg34EpSKed3Gu0FxMFhTJ9OTlgaG38Of0v nnphvIEkQB8+lp8iIVhDe9qP5mqNAfldNd/boN+2HwZiz/s4PZnuk4Hkyj45RncVxt9HdE9 sfP4t6/2Ocu7urejEu1xg== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jun 2014 00:22:03 -0000 Am 12.06.2014 00:36, schrieb O. Hartmann: > > I use my boxes for daily work and in most cases, the usage of applications is the same. > Compiling the OS and updating ports while having claws-mail and firefox opened is some > usual scenario. > > I realise since a couple of weeks, if not months now, but always sticky to 11.0-CURRENT, > that the system is even with 8 GB RAM very quickly out of memory and swapping. As of > today - updating CURRENT (buildword) and also updating ports. Nothing else except > firefox. And the box is using 1% swapspace. Are you using ZFS, and more to the point, did you recently start using it? Do you mean "start swapping out sooner than it used to do"? Do you expect that swap remains at 0 unless there is serious memory pressure? One point: Linux rolls dice when it needs memory, with a tunable that states the chance that either a cached page gets evicted, or an in-use page gets swapped out. Has FreeBSD similar mechanisms these days? > There are some strange behaviours when compiling ports or the OS itself sometimes. I very > often linker errors with something like > > [...] relocation truncated to fit: R_X86_64_PC32 [...] > > This strange behaviour sometimes occurs immediately I switched on the box and start > updating and building world (nothing else done so far) or updating a port. When this > error occurs, I reboot and do the very same job again - and then suddenly it works. It > seems I can not reproduce this problem either. It occurs on 11.0-CURRENT since a couple > of weeks by now and affects different hardware types (as with the unspecific swapping > experience mentioned above, either 8GB and 32GB, but it occurs on the 8GB bixes much more > often than on the 32GB system). Given memory checks did not turn up anything: Are you sure that case/memory/chipset/CPU cooling are still intact and not hindered by dust?