Wired memory analysis
ddb at neosystem.org
Thu Jan 17 04:00:34 PST 2019
After recent update (from 184.108.40.206.g5c117 to 220.127.116.11.g9ea75) my system
regularly runs out of swap space during daily periodic(8) (which is
shifted to 1pm as the system doesn't run 24/7). Sometimes the system runs
out of memory and kills processes, most often chrome, but X also got hit
at least one time.
When inspecting the system during this unpleasant situation, I've noticed
quite high numbers under "wired memory" in top(1). It's a little above
1000M when the system boots and desktop is launched, it gets to around
3500M after cca 5 hours of "normal" desktop usage, but I've seen more then
6000M after periodic(8). What's remarkable, when "wired" gets that high, it
doesn't drop significantly even after periodic(8) is done.
The system has 8G of memory, and it hasn't been utilizing it's 512M of swap
such heavily before the mentioned update. In fact, it's been barely touching
Is there a way one can inspect the content of "wired memory" (and
potentially identify most hungry consumer)? (I know it's _wired_ but) is
there a way a system can be forced to release some of this memory?
More information about the Users