Discussion:
Help needed re-enabling compressed virtual memory.
Michael
2018-04-07 19:57:31 UTC
Permalink
So a while back, I disabled compressed virtual memory:

bash-3.2# nvram boot-args
boot-args -v -s vm_compressor=1
bash-3.2#

I tried to reenable it (removing the vm_compressor argument). Unfortunately, all that did was give me a swap error as soon as physical memory filled up.

I'd like to know what I need to do to go back to compressing my virtual memory.

At the time, my reason for disabling it was that it turned my 16 GB machine into a 6 GB machine. The system would insist on using 10 GB for compressed swap, and my working set at the time -- Minecraft client, Minecraft server, recording software, voice chat software, etc. -- needed more memory than that.


---
Entertaining minecraft videos
http://YouTube.com/keybounce
Carl Hoefs
2018-04-07 20:25:16 UTC
Permalink
I think just clearing the setting will revert to the default behavior (compressing memory):

sudo nvram -d boot-args

Then reboot.

-Carl
Post by Michael
bash-3.2# nvram boot-args
boot-args -v -s vm_compressor=1
bash-3.2#
I tried to reenable it (removing the vm_compressor argument). Unfortunately, all that did was give me a swap error as soon as physical memory filled up.
I'd like to know what I need to do to go back to compressing my virtual memory.
At the time, my reason for disabling it was that it turned my 16 GB machine into a 6 GB machine. The system would insist on using 10 GB for compressed swap, and my working set at the time -- Minecraft client, Minecraft server, recording software, voice chat software, etc. -- needed more memory than that.
---
Entertaining minecraft videos
http://YouTube.com/keybounce
_______________________________________________
MacOSX-talk mailing list
http://www.omnigroup.com/mailman/listinfo/macosx-talk
Michael
2018-04-12 17:55:29 UTC
Permalink
Post by Carl Hoefs
sudo nvram -d boot-args
Then reboot.
-Carl
Nope.

This happens with zero swap space used. In other words, as soon as compressed swap tries to use the disk, it fails.

So my computer:
*can use normal swap, but not compressed swap.
*Can only boot (startup disk) from a normal partition on the internal drive (not from a USB stick, not from the recovery partition)
*refuses to display the boot chooser on pressing alt/option.

All of these used to work. It looks like I was able to boot from a USB stick in January or February (I had to use 10.2 to compact a sparse image that used large bands). I'm not sure when compressed swap failed -- it's probably been a year since I turned it off.

Apr 12 10:41:01 keybounceMBP kernel[0]: low swap: suspending pid 891 (firefox)
Apr 12 10:41:01 keybounceMBP kernel[0]: low swap: suspending pid 853 (Dragon Dictate)
Apr 12 10:41:01 keybounceMBP kernel[0]: memorystatus_thread: idle exiting pid 231 [xpcd]
Apr 12 10:41:01 keybounceMBP kernel[0]: (default pager): [KERNEL]: Swap File Error.
Apr 12 10:41:01 keybounceMBP com.apple.launchd[1] (com.apple.xpcd.CA000000-0000-0000-0000-000000000000[231]): Exited: Killed: 9
Apr 12 10:41:01 keybounceMBP loginwindow[312]: -[ProcessPanel(lowMem) initAsLoMemPanel] | Lo-Memory panel initializing
Apr 12 10:41:02 keybounceMBP kernel[0]: memorystatus_thread: idle exiting pid 235 [com.apple.audio.]
Apr 12 10:41:02 keybounceMBP com.apple.launchd[1] (com.apple.audio.DriverHelper[235]): Exited: Killed: 9
Apr 12 10:41:03 keybounceMBP kernel[0]: memorystatus_thread: idle exiting pid 241 [com.apple.audio.]
Apr 12 10:41:03 keybounceMBP com.apple.launchd[1] (com.apple.audio.SandboxHelper[241]): Exited: Killed: 9
Apr 12 10:41:03 keybounceMBP kernel[0]: memorystatus_thread: idle exiting pid 85 [wdhelper]
Apr 12 10:41:03 keybounceMBP com.apple.launchd[1] (com.apple.wdhelper[85]): Exited: Killed: 9
Apr 12 10:41:04 keybounceMBP kernel[0]: memorystatus_thread: idle exiting pid 407 [IMDPersistenceAg]
Apr 12 10:41:04 keybounceMBP com.apple.launchd[1] (com.apple.imdpersistence.IMDPersistenceAgent[407]): Exited: Killed: 9
Apr 12 10:41:04 keybounceMBP kernel[0]: memorystatus_thread: idle exiting pid 425 [com.apple.NotesM]
Apr 12 10:41:04 keybounceMBP com.apple.launchd[1] (com.apple.NotesMigratorService[425]): Exited: Killed: 9
Apr 12 10:41:05 keybounceMBP kernel[0]: memorystatus_thread: idle exiting pid 406 [xpcd]
Apr 12 10:41:05 keybounceMBP com.apple.launchd[1] (com.apple.xpcd.37000000-0000-0000-0000-000000000000[406]): Exited: Killed: 9
Apr 12 10:41:05 keybounceMBP kernel[0]: memorystatus_thread: idle exiting pid 486 [CloudKeychainPro]
Apr 12 10:41:05 keybounceMBP secd[411]: handle_xpc_event >>>>> handle_connection_event via event_handler <<<<<, WTF?
Apr 12 10:41:05 keybounceMBP com.apple.launchd.peruser.502[259] (com.apple.security.cloudkeychainproxy3[486]): Idle-exit job was jettisoned. Will bypass throttle interval for next on-demand launch.
Apr 12 10:41:05 keybounceMBP com.apple.launchd.peruser.502[259] (com.apple.security.cloudkeychainproxy3[486]): assertion failed: 13F1911: launchd + 43321 [364E35A7-9FA7-3950-8494-40B49A2E7250]: 0x9
Apr 12 10:41:06 keybounceMBP kernel[0]: memorystatus_thread: idle exiting pid 436 [nsnetworkd]
Post by Carl Hoefs
Post by Michael
bash-3.2# nvram boot-args
boot-args -v -s vm_compressor=1
bash-3.2#
I tried to reenable it (removing the vm_compressor argument). Unfortunately, all that did was give me a swap error as soon as physical memory filled up.
I'd like to know what I need to do to go back to compressing my virtual memory.
At the time, my reason for disabling it was that it turned my 16 GB machine into a 6 GB machine. The system would insist on using 10 GB for compressed swap, and my working set at the time -- Minecraft client, Minecraft server, recording software, voice chat software, etc. -- needed more memory than that.
---
Entertaining minecraft videos
http://YouTube.com/keybounce
_______________________________________________
MacOSX-talk mailing list
http://www.omnigroup.com/mailman/listinfo/macosx-talk
---
Entertaining minecraft videos
http://YouTube.com/keybounce

Continue reading on narkive:
Loading...