|
|
RE: why bother in the year 2002?
You know back when RAM cost about $500 per megabyte and a 10 MB hard drive cost about the same we used to really worry about optimizing virtual memory performance because it really did make a difference--like in the 500-1000% performance improvement difference for compute intensive tasks. But the performance benefit you get with modern hard disks and the huge amounts of RAM and disk space available makes all of this pretty much mental masturbation for doing this on OS X. People report all sorts of subjective improvements, but the actual numbers provided by proponents of this technique are amazingly short of impressive. To get a "real" benefit you ought to be putting the vm space on a 0 striped LVD SCSI array which costs a whole lot more than just buying RAM. And that real benefit will only buy you a handful of percentage points improvement. I'm sure people are wasting more time trying to do this than they are actually gaining.
RE: why bother in the year 2002?
For most users, raw VM performance is a secondary reason to move your swap space (i.e. if you're doing it just to get better performance, you're probably wasting your time). The real reason to move swap is to get it into an area where there's no competition. You can't run out of swap space if something goes nuts and fills up your boot partition, you can't get a fragmented swap file because your boot partition is fragmented, etc. It makes your swap space behavior consistent and predicatable, and that's a good thing.
RE: why bother in the year 2002?
The answer to all of this is to AVOID swapping all together.
RE: why bother in the year 2002?
I have 1.2 GB ram and I still get pageouts (91595(0)). With the swap on an separate drive I don't see the spinning lolipop very often as opposed to several second waits here and there without moving swap. Besides pageins require a read of the swapfile thus causing some minor thrashing. Pageouts require reads and writes causing thrashing.
RE: why bother in the year 2002?
From your swapping activity I would venture to say you're overloading your system and/or you're using programs that employ poor memory management strategies.
RE: why bother in the year 2002?
Don't worry about pageins and pageouts unless you're getting lots of them while apps are running. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.05 seconds |
|