Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Don't quit apps - hide them! System
One of the big beefs most folks have with OS X is application launch times. But one of the great things about OS X is its virtual memory system. This can be used to avoid waiting for applications to launch.

If you hide (command-H) an application when you're done using it instead of quitting it, you avoid the delay which occurs when you need to use that application again. There's almost no penalty for doing this, except perhaps a slightly overcrowded dock.

Now, for example, when you want to view a help page, you'll get to view it immediately, rather than having to wait for the Help application to launch.

[Editor's note: There's almost no penalty to a point. If you start to hear lots and lots of hard drive activity, you're probably pushing the limit. The more RAM you have, obviously, the more apps you can leave open.]
  • Currently 2.67 / 5
  You rated: 2 / 5 (3 votes cast)

Don't quit apps - hide them! | 5 comments | Create New Account
Click here to return to the 'Don't quit apps - hide them!' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
What about classic apps?
Authored by: Loren on Jun 04, '01 11:45:47AM

Does this apply to classic apps too, or should we still quit them?

[ Reply to This | # ]
Re: What about classic apps?
Authored by: Anonymous on Jun 05, '01 05:46:31AM

Classic Apps also benefit from the advanced Memory Managements, but there is a reason, why you don't want to have too many classic apps running: Every Classic App can crash the Classic environment (i.e. all other classic apps) but if your app is stable and you have saved your work, you may do as you please. (Classic apps do lauch quite fast under Mac OS X form my experience).

Oh, and you should hide classic apps, when you put the machine to sleep. otherwise you might loose the nearly instant wakeup.


[ Reply to This | # ]
Unix VM
Authored by: sharumpe on Jun 04, '01 04:51:26PM

The editor's comment isn't strictly true. You can keep many programs open, and only incur massive paging hits when programs with large memory footprints are moved in or out of real memory. If the program being paged out to disk is using a lot of memory, then it takes a long time to page (relative to others). The same is true in reverse.

So, if you have lots of small programs open (small relative to physical memory), you don't get much paging when switching between them, even when you've exceeded 'real' memory.

It is more complicated than that, but that's pretty close. When you exceed your physical memory, it doesn't dump the whole contents of memory, just what it needs.

[ Reply to This | # ]
Unix VM
Authored by: pascalpp on Jun 04, '01 08:16:46PM

...and I would imagine that paging a large application to or from disk would almost never take longer than it would currently take to relaunch said application after quitting it.

[ Reply to This | # ]
Unix VM
Authored by: kon21 on Jun 05, '01 08:38:03PM

a good way to figure out if you are out of memory is to use the TOP command in the terminal. you will notice and area with 'x(0) pageins, 0(0) pageouts' if you see the pageouts grow then you know you are using your hard drive for memory.

[ Reply to This | # ]