Skip navigation

Inactive memory is huge hit on performance

41979 Views 145 Replies Latest reply: Dec 30, 2013 8:57 AM by macintosh_fred RSS
  • CT Level 6 Level 6 (14,985 points)
    Currently Being Moderated
    Nov 16, 2012 1:50 PM (in response to CathyHeaton)

    You need a bigger pie.

  • David M Brewer Level 6 Level 6 (9,180 points)
    Currently Being Moderated
    Nov 16, 2012 1:54 PM (in response to CT)

    All right now... who took a peice of the pie... come on now.... fess up.

  • paulba71 Calculating status...
    Currently Being Moderated
    Nov 16, 2012 2:35 PM (in response to Joasousa)

    Problem solved for me anyway - I've installed Windows 8 through bootcamp and I no longer get any performance issues. I have a quick, smooth and professional operating system running on my iMac now and I can think of no reason in the world why I'll boot into the old, buggy, performance hog that is mac OSX ever again.

    And as a bi-product I can simply unplug my USB storage devices without having to unmount them and run the risk of losing data.

    Result!!!!

  • pjw23 Calculating status...
    Currently Being Moderated
    Jan 30, 2013 6:14 AM (in response to Joasousa)

    Inactive memory....had this problem myself on my 24" imac. I solved it by doing this:

     

     

    1) Cleared and tidied HD

    2) Reset ram by taking them out a little bit and putting them back in

    3) reinstalled OSX

    4) NEW SPEED IS BACK

    5) clear caches as a finishing touch

     

    All sorted

  • Ai-Max Calculating status...
    Currently Being Moderated
    Mar 21, 2013 10:27 AM (in response to thomas_r.)

    @ Thomas A Reed,

    I have been reading everything I can on this forum and othres about the apparent " issue " of the " inactive memory " in Mac OSX. I have been a Mac user for long time ( My Mac Clasic II still runs ) and I will be for long to come unless they become another Microsoft.

     

    Something that started getting annoyoing with your replys to members is the monotone, deny all, fanboy attitude.

    Could you please participate in a constructive way in this issue you have been working hard to deny.

     

    I just picked up a brand new iMac from Apple store ( iMac 2012 - i7- HD,2TB -  24 GiGRAM - 2GiG Video ).

    The only thing on this Machine is the OS and standard APPLE included apps. Just by running safari the " Inactive Memory " has gone up to 20 GB.

    You and I and a lot other Mac users around here know well enough if I try to install ... let's say Apperture at this state of my machine I will receive a Low Memory dialog box.

     

    The question is : Is this an acceptable scenario or not ?

  • David M Brewer Level 6 Level 6 (9,180 points)
    Currently Being Moderated
    Mar 21, 2013 10:34 AM (in response to Ai-Max)

    I don't have any problems. Does Safari go up to 20 gigs on the Apple's web site? If not it is the web site (that your are visiting) that is the problem. There are so many poorly written web sites (especially using out dated and poorly written javascript.) out there that muck-up a persons computer.

  • Ai-Max Level 1 Level 1 (0 points)
    Currently Being Moderated
    Mar 21, 2013 11:20 AM (in response to David M Brewer)

    @David M Brewer,

     

    No I didn't specifically stayed on APPLE's site. LOL

    I have been reading disgruntle postings about the Inactive Memory where I can - mostly in here.

     

    At this point it's obvious to me that APPLE have decided to exchange the perception of speed and responsiveness of the OS to the Memory issues by piling all they can and keeping them in the available memory.

    There must be a happy middle ground.

     

    Soon I have to Maxout the RAM on this machine and go to work. Most of the time I will be running RAM hungry apps ( Photoshop - FCPX - AfterEffects - MochaPro ) in parallel non of which has to do anything with JAVA - although they use ( abuse ) the RAM with other means.

     

    One interesting thread on Cinema4D forum is suggesting that soon RAM will be integrated to the main Memory when SSDs are developed enough and that's the reason APPLE is not paying attention to all this unhappy noise coming from the community. What do you think of that ?

  • Salda Calculating status...
    Currently Being Moderated
    Mar 26, 2013 11:32 AM (in response to Joasousa)

    Just came across this, after fighting my machine since the day I upgraded from SL to ML. Running 16GB of RAM in my MBP, PS CS5 is setup to use a little under half of that as it's my main workhorse. Installed Memory Clean to monitor & purge, routinely, it shows free memory at <1GB in the menu bar, during which everything slows to a crawl. Purge the RAM, and everything returns back to normal, free memory returns to 4-5 GB and I can get back to work.

     

    IF INACTIVE AND FREE MEMORY ARE THE SAME in Apple's engineering eyes, then why does the above process work? For some reason the OS does not access or release the inactive memory when a process is needing it.

  • notevenhardly Calculating status...
    Currently Being Moderated
    Apr 9, 2013 10:49 PM (in response to Salda)

    This has always happened with me, 24GB RAM, from Leopard through Snow Leopard. This is not a hardware issue and it isn't going to change reseating or swapping the RAM. It is what happens with memory-intensive work. Restarting the machine frees up 'inactive'. Sometimes the OS can use the inactive if I unload what's actually using RAM and reload it or the same type. Sometimes it simply holds onto all of this blue chunk. I am using heavy samples library use for music/audio. I just had some page outs - with 24GB RAM - where I was using really around 11GB. That's ~0GB in the blue. It is absurd. Typically I don't kvetch as I know I can restart and get the free memory back. sometimes this is really no good like tonight.


    It absolutely is not a matter of not understanding how to maintain things. This is fanboy garbagio and just kind of insulting to the intelligence to see.
    I would love to be able to say, OSX uses RAM as well or better than Windows (I don't care for Windows at_all.). It does not. It is notorious for this. The developers of what I'm using [VSL] call this 'the pitfalls of OSX'. I'm sure they know what they're doing.

  • petermac87 Level 5 Level 5 (4,065 points)
    Currently Being Moderated
    Apr 9, 2013 11:29 PM (in response to notevenhardly)

    notevenhardly wrote:

     

    This has always happened with me, 24GB RAM, from Leopard through Snow Leopard. This is not a hardware issue and it isn't going to change reseating or swapping the RAM. It is what happens with memory-intensive work. Restarting the machine frees up 'inactive'. Sometimes the OS can use the inactive if I unload what's actually using RAM and reload it or the same type. Sometimes it simply holds onto all of this blue chunk. I am using heavy samples library use for music/audio. I just had some page outs - with 24GB RAM - where I was using really around 11GB. That's ~0GB in the blue. It is absurd. Typically I don't kvetch as I know I can restart and get the free memory back. sometimes this is really no good like tonight.


    It absolutely is not a matter of not understanding how to maintain things. This is fanboy garbagio and just kind of insulting to the intelligence to see.
    I would love to be able to say, OSX uses RAM as well or better than Windows (I don't care for Windows at_all.). It does not. It is notorious for this. The developers of what I'm using [VSL] call this 'the pitfalls of OSX'. I'm sure they know what they're doing.

    I have 8GB Ram, currently have open Illustrator, InDesign, Photoshop, Aperture, Logic and Word as well as running Mail and Safari. Everything is responding 100% so it is not a problem for everyone. So what is VSL out of interest?

     

    Thanks

     

    Pete

  • vibration888 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Apr 9, 2013 11:54 PM (in response to notevenhardly)

    UNIX based OSX was known by audio app developers to not be the best solution for audio. But having a secure and stable OS was more important. So we live with it. When I was running my DAW and Kontakt (with mem server running) in 32-bit mode, I had the same problem you're having. Once I got rid of all my 32-bit apps and only ran 64-bit the problem went away.

     

    Without knowing your situation, my first guess is that it's a 32-bit DAW or sampler that's not cleaning up after itself.

  • notevenhardly Level 1 Level 1 (0 points)
    Currently Being Moderated
    Apr 10, 2013 11:04 AM (in response to petermac87)

    [correction of typo, that was supposed to read '~10GB in the blue'; inactive, at the end of that day useless memory.]

     

    VSL is Vienna Symphonic Library. This is nothing to do with 32-bit. I don't run KMS, I run Kontakt as x64 in Vienna Ensemble Pro x64 server.

     

    if the 'purge' command works - I read last night it ceased to work for someone - that would sort the issue I experience. It looked like 'Free Memory' works not at all here, as though it requires Lion OS.

     

    Without going into detail, I believe this issue is all Apple.

  • notevenhardly Level 1 Level 1 (0 points)
    Currently Being Moderated
    Apr 10, 2013 11:09 AM (in response to notevenhardly)

    the issue for me as per the thread title is that I saw page outs. with 24GB I'm having page outs using 10, 11 GB in actual processes? Yeah, I live with it, I usually am fine with 'reboot and get on with it'. I came across this thread looking for something to free up the RAM after a particularly stupid situation last night.

  • Bill3Smith Calculating status...
    Currently Being Moderated
    Apr 10, 2013 12:22 PM (in response to notevenhardly)

    I got on this thread quite a while ago... but I haven't been following it too closely lately, so apologies in advance if someone recently posted the following solution I saw earlier in the discussion.  It has eliminated for me the need to reboot in order to fix this problem.  ; ) 

     

    You just install the 'Developer Tools' from your OS X disc (Snow Leopard, in my case) and then to regain use of any 'locked-up' memory, you just open up Terminal, type 'purge', hit enter, and after a few seconds that frees your memory up for whatever you want to use it for next.

     

    Note: This probably isn't going to be a good solution for anyone wanting to solve the problem without losing any data in currently-open programs, perhaps... but it is faster than a reboot.

     

    I have typed 'purge' in Terminal once or twice with a couple of software programs open, and it didn't shut them down at least... but I haven't tried it too much at all with programs left running and documents/files being worked on. 

     

    Does anyone know if you can use this 'purge' command *with* documents open or image/video files being worked on, and not cause any problems such as losing un-saved data, etc.?

     

    Or for example during an EyeTV recording while it is being made, typing 'purge' then would be a good test.  I may try it and post later if it screws up the recording...  Cheers and good luck, y'all.

  • Salda Level 2 Level 2 (235 points)
    Currently Being Moderated
    Apr 10, 2013 12:31 PM (in response to petermac87)

    petermac87 wrote:

     

    I have 8GB Ram, currently have open Illustrator, InDesign, Photoshop, Aperture, Logic and Word as well as running Mail and Safari. Everything is responding 100% so it is not a problem for everyone. So what is VSL out of interest?

     

    Thanks

     

    Pete

     

    It's not a matter of how many programs you have open. Open up 2 or 3 Photoshop files that are +2GB. They don't even have to be open at the same time, open one, close, open another, close, etc. My system (16GB) starts to crawl with that type of workload. Once I run the purge command (sometimes even after closing PS), all returns to normal.

1 ... 4 5 6 7 8 ... 10 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (4)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.