Message-Id: <m0yyz2w-000S4xC@inti.gov.ar>
Comments: Authenticated sender is <salvador AT natacha DOT inti DOT gov DOT ar>
From: "Salvador Eduardo Tropea (SET)" <salvador AT inti DOT gov DOT ar>
Organization: INTI
To: ams AT ludd DOT luth DOT se (Martin Str|mberg), djgpp AT delorie DOT com
Date: Wed, 22 Jul 1998 10:44:15 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: EMM386 limiting memory to 32Mb
In-reply-to: <6p31qq$j6$1@news.luth.se>
Precedence: bulk

Abouthe ams AT ludd DOT luth DOT se (Martin Str|mberg) reply to Eli:

MatinS:

  You are lossing the point. What Eli says is that you must have X Mb 
of swap, he says that X Mb is the better choice. (or at least I 
interpret that ;-)
  Normally you must put some limits to the relation 
between: Physical/Virtual to avoid huge performance degradations. 
  As an example: Windows 3.1 sets a maximun value, you can enlarge 
the swap even further, but Windows won't use it.
  CWSDPMI doesn't have any  limit, that's good because you can 
compile a program that needs 128 Mb of RAM with only 16 Mb. But if 
you need to do it very often a good minimal limit is:  48Mb of RAM 
and 80Mb of swap. Of course you can do it with 16/112, not 
recommended at all.

SET
------------------------------------ 0 --------------------------------
Visit my home page: http://set-soft.home.ml.org/
or
http://www.geocities.com/SiliconValley/Vista/6552/
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org
ICQ: 2951574
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA
TE: +(541) 759 0013