Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Going from 2.3gb page ins and 150mb of page outs to 1.6gb of page outs in only a matter of hours is definitely something to worry about, and it's definitely a memory issue. It also confirms what I've heard about vmfusion-- it demands a large amount of memory to perform without lag (compared to parallels)

An 800mb swap size is stupendously huge too.

im sorry, but what :eek: ? thats not correct at all. when using VMs that DEMAND 2GB dedicated memory (in this instance) you are GOING to have page outs from other programs and you are going to have swap memory increasing as a result of that. page outs are not a bad thing - they are actually a good thing, would you rather the VM memory being chucked into VM (virtual memory) directly?

currently i have::

VM: 236GB
page ins: 9.8GB
page outs: 6.97GB
swap: 5.30GB

you must remember that these numbers are cumulatory (is that a word lol?) numbers - i am running a VM with 1GB RAM assigned to it on my iMac i7. my computer is just as responsive as any other. sure i would LOVE to see some free memory, but that will need to wait until i have some :)
 
No, I don't think you know what you're talking about.

spinnerlys linked the page as the very first response to this topic:
http://support.apple.com/kb/HT1342

Page outs are when your computer has to access the hard drive of the computer for writing information, it's a very inefficient process, thus slows down your computer.

10gb of page ins and 7gb of page outs? You need more ram.


My iMac currently has 13gb page ins and 0mb of page outs. Pretty good I say :)
 
No, I don't think you know what you're talking about.

spinnerlys linked the page as the very first response to this topic:
http://support.apple.com/kb/HT1342

Page outs are when your computer has to access the hard drive of the computer for writing information, it's a very inefficient process, thus slows down your computer.

10gb of page ins and 7gb of page outs? You need more ram.


My iMac currently has 13gb page ins and 0mb of page outs. Pretty good I say :)

page outs and ins will happen regardless - as OSX moves some pages into there after certain amounts of inactivity. no matter what.

i know all about page outs, ins, swaps and VM in general. i have looked into the processes in a fair bit of depth, certainly miles more then what that article is that spinnerlys linked to thats for sure.

im not arguing that they dont slow the computer down, of course they do - but having 800MB of swap is not as bad as you make it out to be!

back on topic, i dont think its a RAM issue.
 

Attachments

  • Screen shot 2010-06-19 at 10.38.28 PM.png
    Screen shot 2010-06-19 at 10.38.28 PM.png
    194.8 KB · Views: 38
page outs and ins will happen regardless - as OSX moves some pages into there after certain amounts of inactivity. no matter what.

i know all about page outs, ins, swaps and VM in general. i have looked into the processes in a fair bit of depth, certainly miles more then what that article is that spinnerlys linked to thats for sure.

im not arguing that they dont slow the computer down, of course they do - but having 800MB of swap is not as bad as you make it out to be!

back on topic, i dont think its a RAM issue.



No, pages out do NOT happen regardless. Page outs happen when the OS becomes memory constrained, and a few special cases.

This is from the Apple Support page:

Tip: Page outs occur when your Mac has to write information from RAM to the hard drive (because RAM is full). Adding more RAM may reduce page outs.



Page out are bad, always bad. The only thing to discuss is exactly how bad.

Also, for those that don't understand this I'd like to explain why paging is bad.

When an OS (Mac OS, Windows, Unix, etc) runs out of memory it writes a block (or page) of memory to disk. This is called paging. The process of moving the read/write head on your drive and then writing the used but inactive memory out. Sooner or later, the OS has to go and read that memory back in. This process can repeat itself many times per second. Needless to say, disk access times are many orders of magnitude slower than memory access times. And oh, by the way, if you were performing any sort of disk IO, you will now also have disk contention with the paging process. This is all extremely bad. This is why no OS EVER pages unless it absolutely has to. This is also why paging kills system performance more than anything else. Paging idles you CPU greatly and introduces IO performance penalties.

The only 3 option in order of best to worst are:

1) Get more memory. This is usually the best option.

2) Free up existing memory. The assumption though is that you would have if you could have.

3) Get a faster drive to increase paging performance or place your swap on a different drive to reduce drive contention. This is old school but Unix admins used to to this all the time in the 90... It help but still sucked.

If I got something wrong, please let me know. This is really a simple problem though.
 
ive been running VMware fusion on mine, and this week while browsing (no vm) i got a kernel panic error, and it turned out to be ram failure...
ive been wondering if running vmware fusion so much caused or contributed to it..
 
If your operating system's resorting to page outs, and your hard drive has little free room left, you'll start getting kernel panics among other things.
 
If your operating system's resorting to page outs, and your hard drive has little free room left, you'll start getting kernel panics among other things.

what are page outs? i had plenty of hdd space... im really paranoid now, i havent installed vmware fusion on my new mbp (apple replaced my mbp when i brought it there after the kernel panic error)
 
what are page outs? i had plenty of hdd space... im really paranoid now, i havent installed vmware fusion on my new mbp (apple replaced my mbp when i brought it there after the kernel panic error)

Mac OS X: Reading system memory usage in Activity Monitor

Page ins / Page outs

This refers to the amount of information moved between RAM and the hard disk. This number is a cumulative amount of data that Mac OS X has moved between RAM and disk space.

Tip: Page outs occur when your Mac has to write information from RAM to the hard drive (because RAM is full). Adding more RAM may reduce page outs.
 
No, pages out do NOT happen regardless. Page outs happen when the OS becomes memory constrained, and a few special cases.

I think it might be worth you reading this. Saying 'special cases' doesn't let you get away with the basic baloney that you just said. Like I stated before, given the right amount of time, page outs happen regardless. Apple is simplifying the page for their general reasons to get more money, make it easy for users to understand etc. Don't get caught in their simplistic ways. :rolleyes: unix is amazingly complex.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.