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

Click here to return to the 'RE: why bother in the year 2002?' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
RE: why bother in the year 2002?
Authored by: WillyT on Oct 17, '02 10:32:27AM

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.

Put it on a separate disk and all that is just a distant memory.
The only time I need to worry about mount order is during a reboot. Come up in single-user fsck and fsck_hfs everybody and exit. If everything looks good for fsck_hfs then the swap will come up right. If fsck_hfs -y /dev/disk0s10 shows something other than Swap then just reboot again. My uptime is nine days right now (would be more if shutdown now worked) so you see I don't worry about this every day.

[ Reply to This | # ]
RE: why bother in the year 2002?
Authored by: barrysharp on Oct 17, '02 11:06:11AM

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.

I guess it's possible you launch programs that you use infrequently. This means that once they or a portion of them reside in physical memory and they lay dormant they have to be swapped out (paged out in bits and pieces) to make room for other programs you launch.

If you aren't going to use a program for some time then simply quit it and release the valuable memory resources it's consuming back to the system for reuse by other more important and *frequently* used programs you use.

Quitting a program will also protect it from a system crash in that if it's still memory resident or active at the time the system crashes there's danger that some of it's data hasn't made it to disk for permanent safe keeping.

I also think a large fast HD dedicated to scratch files is of benefit as i/o is more likely to find big contiguous chunks of space to speed up data transfers. However, many programs don't provide the option to direct their scratch data to specific HD locations. Yes, there are some exceptions to this such as PS but many still remain that don't offer this.

My experience has told me to avoid swapping like the plague.

Now, as we start having the option of using multi processor machines such as Apple is deploying today in their G4 tower line the question of swapping becomes a little more interesting. With these systems it matters little if swapping is occuring so long as the CPUs aren't being starved because of such action or because of the swappin interferring with outher non-swapping activities. Having a separate HD for swapping may be a more worthwhile endeavor under these circumstances.

Regards... Barry Sharp

[ Reply to This | # ]
RE: why bother in the year 2002?
Authored by: robh on Nov 09, '02 04:23:55PM

Don't worry about pageins and pageouts unless you're getting lots of them while apps are running.

Chances are, you're getting them when starting apps or bringing them to the foreground after a long period of inactivity.

Now if you are running apps and you see tons of pageins/outs then you probably are very short of physical memory and hammering swap space. In these cases, throw a few bucks at the problem and add more RAM, it'll have a massively greater effect on the problem than moving the swapspace.

IMO, moving the swapspace on an OSX box is a complete waste of time and effort.

[ Reply to This | # ]