Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 12 Jun 2014 00:36:12 +0200
From:      "O. Hartmann" <ohartman@zedat.fu-berlin.de>
To:        FreeBSD CURRENT <freebsd-current@freebsd.org>
Subject:   CURRENT: why is CURRENT swapping so fast?
Message-ID:  <20140612003612.25cc2851.ohartman@zedat.fu-berlin.de>

next in thread | raw e-mail | index | archive | help

[-- Attachment #1 --]

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

[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBAgAGBQJTmNnhAAoJEOgBcD7A/5N8d/cIAIc6aXFnw1qxEmIShJFu9Y8U
s+iPVcgOUdgwcsPEn6oD5afwlDGNKopiTQiw1vcP2LhCkpshJ2IlJugsdbzXRXZa
dqj/E5DN8TOAh6Uhb6Mv50QvXgi4JlBqiayj1dFhy++7yMwbiB3+e9QenT8fHyfj
Qb8jkQHzzG2cKlStgKkcrkQ3Tc6hKpTitakb8CnF/x+LNpJimX42x4icDygDvAum
w2bbxiYldg8U1EoOd4oIpq/FN6sV4X2UpkV1MWlR6uXn1bUXClEh4Xlja8fafgdj
mtjmVGI4OfdkCpvzlfiCkbnN12RYdrJun7veWlQ2vH7s/fb72t3Z7RF+RI7niWo=
=C+7X
-----END PGP SIGNATURE-----

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140612003612.25cc2851.ohartman>