home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!portal!lll-winken!fnnews.fnal.gov!mp.cs.niu.edu!ux1.cso.uiuc.edu!news.cso.uiuc.edu!usenet
- From: shair@barolo.cso.uiuc.edu (Bob Shair)
- Newsgroups: comp.unix.aix
- Subject: Re: Virtual Memory curiosity
- Keywords: VM overflow response
- Message-ID: <BxMACn.I6H@news.cso.uiuc.edu>
- Date: 12 Nov 92 19:05:08 GMT
- References: <bmarlowe.721422470@ka> <BxM5C5.Jyw@csn.org>
- Sender: usenet@news.cso.uiuc.edu (Net Noise owner)
- Reply-To: shair@vnet.ibm.com
- Distribution: usa
- Organization: IBM Champaign
- Lines: 28
-
- losburn@teal.csn.org (Lynn Osburn) writes:
-
- >>I've heard rumor that AIX will pick processes to kill off to avoid
- >>running out of virtual memory?
- >
- >True in v3.1.x
- >
- >False in v3.2.x
- >In 3.2, he just picks the larger process(es) and puts them to sleep (and
- >swaps them) for a while until things improve. A much better solution to
- >the problem, eh?
-
- True or false depending on what you mean by "running out of virtual memory."
-
- When you overcommit real storage, so the system is thrashing (paging heavily),
- AIX 3.2 sleeps processes as Lynn states.
-
- If you run out of swap space, though, AIX will pick processes to kill off.
- This is true both in 3.1 and 3.2. The algorithm used to select the processes
- to kill has changed, I hear, but I don't know what it is.
-
- Anyone do?
-
- --
-
- Bob Shair shair@vnet.ibm.com
- Scientific Computing Specialist SHAIR@UIUCVMD (bitnet)
- IBM Champaign
-