delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1998/05/07/03:05:48

Date: Thu, 7 May 1998 10:05:22 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: James W Sager Iii <sager+@andrew.cmu.edu>
cc: djgpp AT delorie DOT com
Subject: Re: Meja-slow down
In-Reply-To: <cpIF86O00YUn0nlGM0@andrew.cmu.edu>
Message-ID: <Pine.SUN.3.91.980507100501.5259B-100000@is>
MIME-Version: 1.0

On Wed, 6 May 1998, James W Sager Iii wrote:

> I get the stats 2923kb and 130389kb from the go32-v2 command
                  ^^^^^^
2.9MB is way too few.  Your 4MB program will page to disk like heck
  and will run very slowly indeed.

> DEVICEHIGH=C:\windows\EMM386.EXE /8128 frame=NONE

Why do you need these parameters on the EMM command line?  If this is
DOS 6 or later, you don't need the 8128, and I would also try without
frame=NONE.

> devicehigh=c:\windows\ramdrive.sys 4086 /e

This is okay.

> loadhigh=c:\windows\smartdrv 16384 /n/f
                               ^^^^^
This is NOT okay!  You are creating a 16MB disk cache on a 24MB
machine, so you only leave yourself 4MB (since another 4MB went to a
RAM disk).  Make the cache be 4-6MB, and you will have tremendous
performance boost.

Note that the FAQ doesn't recommend to set aside more than 8MB for the
cache, even if you have plenty of RAM (which 24MB is not).  the rule
of thumb is to leave at least 8MB free after installing the disk cache
and the RAM disk.  16MB free is even better, especially if you need to
run large programs like RHIDE.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019