Date: Wed, 11 Jun 2014 23:47:11 -0400 From: Allan Jude <allanjude@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: CURRENT: why is CURRENT swapping so fast? Message-ID: <539922BF.1060105@freebsd.org> In-Reply-To: <20140612003612.25cc2851.ohartman@zedat.fu-berlin.de> References: <20140612003612.25cc2851.ohartman@zedat.fu-berlin.de>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On 2014-06-11 18:36, O. Hartmann wrote: > > 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. > > It is hard to reproduce or give exact numbers or any more scientific values. But the way > I do my work is monotonic and it is more than obvious that the box is swapping much > faster right now than, say, 6 months ago. The problem occurs on different hardware types, > one box has 8 GB, the other 32GB. > > 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). > > I'm sorry about this unspecific reporting, but since I observe this strange behaviour but > can not successfully reproduce it by will I suspect something "faulty". I did already RAM > checks on the systems affected - without any abnormal occurence of memory faults or so. > > Regards, > oh > What does 'top' show. It probably holds the answer or top -S -o res -- Allan Jude [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTmSLCAAoJEJrBFpNRJZKfTjEP/1TZLKJt68D6Zv67pRLILtCH 3J4TBAVK/OK9j4nRdVOoJfP0T+EiuUXklcDOxkFofcxhrl54OpLUZeU0nITNUOr1 iV7ArauBFo5LQt8RJylSCtmwKPAluh+0GYyIJmTWPNedYMdeFOYGHpmytAsNMnGG M1um+6suTkcfIssin0brAp4QLK2zG0OFUItKBSHejdGnJl5RCRITeMZfOCeG+U0N YfnzOKrNSFMnmDzoXhB4IoSG2dp7o6TDPPdtA9Rjfsnd0Om4XsrfpVrVh+0GWyum /kVOb22w6fqSbDWqQ2crSrRtnPnD1scsy3w1s898S0LRIIr3gd7NniTxm8oQK8Th 9PXIO2pD3AGYpJkMFFrq+a1BCnOEtdHmoaz//dERHR1BxHtQb95kJD968At7jhqR 5jiMDOuTazzM6ggw3WFj0TaY1ApkgllbOswf1A7fvcXDFy6SDAzKj4W+yeR1UufX zXtvpEic7ER0lN1xhKrF5m6RxX5V2gXIhV+QfacKeXL2Pc8JMy57xshIzcspg8zb 395wEpcqAmMvIR3VQKcF6KXdPQUo7hJnE/wNvRnJRnSO7eA3qGx9lLPjbCRZ+s7z eVblGNv2z96tWoqaz6sPjFCJ5jxqKD4Q1kKm7waTcxT/zWJWAt52DVROTw5UFHhd HBruOs5vl0V4nh7wKpaB =5Fob -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?539922BF.1060105>