Re: 1.x memory usage

New Message Reply Date view Thread view Subject view Author view

Jim Helman (jimh++at++surreal)
Fri, 04 Feb 94 12:23:36 -0800

Performer prefers availsmem_accounting=0 (note that the variable
goes away in 5.2). Having availsmem_accounting=1 could cause
the problems I described in the previous message regarding
Performer reserving too much swap space for other processes to
run.

I would leave availsmem_accounting=0. I'm not familiar with how FAST
allocates memory, however, I would expect at worst that when FAST runs
out of memory, it will dump core rather than print out an error
message and exit. One of the authors of FAST was a strong advocate
for strict memory accounting (up front rather than when used).

I forgot to mention in my previous mail, that under late 5.1 and
5.2 you can still turn off availsmem accounting by adding a large
section of "virtual swap" To do this:

        su
        # chkconfig vswap on
        # edit /etc/config/vswap.options
                <change vswaplen to a large number like 999999>

The same thing can be achieve by creating a zero length file /somefile
and putting a line in your /etc/fstab or interactively invoking the
swap(1) (swap -a -v 999999 /somefile) command.
           
rgds,

-jim helman

jimh++at++surreal.asd.sgi.com
415/390-1151

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:50:10 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.