Searched but cannot find solution to Page outs vs Inactive memory problem

Discussion in 'Mac Pro' started by iamsilvermember, Jun 10, 2010.

Most Liked Posts
  1. iamsilvermember, Jun 10, 2010

    iamsilvermember macrumors newbie

    Joined:
    Oct 27, 2007
    #1
    Attached is screen shot of memory allocation on my computer. Even there are many GB's of memory inactive, there are no more free ram, page outs is still being utilized...

    I went as far as unloading/disabling dynamic pager by using the command:

    sudo launchtl unload -w /System/Library/LaunchDaemons/com.apple.dynamic_pager.plist

    Which successfully avoided "Swap Used" without any problem after many days of test, but I don't understand why "Page outs" is still huge consider there are so much free ram...

    Any suggestion or idea?

    Thanks in advance!
     

    Attached Files:

    share
    + Quote Reply
  2. Hellhammer, Jun 10, 2010

    Hellhammer Moderator

    Hellhammer

    Staff Member

    Joined:
    Dec 10, 2008
    Location:
    Finland
    #2
    share
    + Quote Reply
  3. Vylen, Jun 10, 2010

    Vylen macrumors 65816

    Joined:
    Jun 3, 2010
    Location:
    Sydney, Australia
    #3
    It's possible that this is normal. While inactive memory essentially equates to bring free, there's no guarantee that giving inactive memory to an application is free - that is, it requires memory in order to clean certain blocks of memory before passing it on. And since you have a small amount of free memory, it needs to page other unused blocks in order to do this.

    Of course, this is speculative until someone who knows the internal memory management system of OS X can confirm or deny this, but I don't think this will happen any time soon.
     
    share
    + Quote Reply
  4. gnasher729, Jun 10, 2010

    gnasher729 macrumors P6

    gnasher729

    Joined:
    Nov 25, 2005
    #4
    500 MB of pagein/out is _nothing_. Stop worrying.
     
    share
    + Quote Reply
  5. DualShock, Jun 10, 2010

    DualShock macrumors 6502

    Joined:
    Jun 29, 2008
    #5
    I believe the answer is your usage of Vuze.

    Torrent clients seem to cache the files they are actively uploading in RAM. I've noticed the same behavior with Transmission.

    If you close down Vuze you'll see that RAM slowly get collected by OS X and reallocated to either active or free memory.
     
    share
    + Quote Reply
(You must log in or sign up to post here.)

Share This Page