Date:	Mon, 19 Oct 92 09:00:40 EDT
From:	DJ Delorie <dj AT athena DOT ctron DOT com>
To:	mcastle AT mcs213k DOT cs DOT umr DOT edu
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	compiling large files

>Also, when building under debug32, I noticed that the paging file started 
>building when there was 20k of real memory free (actually, it may have been
>60k, but it was so long ago, I can't remember).  As the paging file increased
>in size, I noticed the real memory kept decreasing in size until it got down
>to about 8k.  I assume this was for building the page tables.  I'm wondering
>if before I stripped out my 3meg ramdrive and 1meg disk cache, and trying to
>compile with only 4megs of free memory, if it was running out of real memory
>building the virtual memory page tables, thus causing the page fault.

The 20K is reserved for page tables to prevent intense paging on
machines with less than 4Mb of memory.  go32 will page the page tables
if required, and ensuring at least five or six extra pt's reduces the
amount of paging significantly.  Testing this was no picnic.

The most I've ever seen go32 hit (outside of testing) was 5.2Mb
compiling part of gcc with -O2.  I had trouble doing this until I
fixed go32 as described above.

DJ
dj AT ctron DOT com
Life is a banana.

- Raw text -