Xref: news-dnh.mv.net comp.os.msdos.djgpp:4216
Path: news-dnh.mv.net!mv!news.sprintlink.net!cs.utexas.edu!academ!news.sesqui.net!rice!news!sandmann
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: What's with beta4?!  Can you say s-l-o-w?  I need help.
Date: Tue, 09 Jan 1996 14:51:06 CST
Organization: Rice University, Houston, Texas
Lines: 15
Message-ID: <30f2d53a.sandmann@clio.rice.edu>
References: <4cue6r$1a5 AT pith DOT uoregon DOT edu>
Reply-To: sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host: clio.rice.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

> Just last night I downloaded beta4, and recompiled my program with it.
> However, I was forced to switch back to beta3 because beta4 seems to
> produce unbearably slow code.  

This is almost certainly a byproduct of not upgrading CWSDPMI at the
same time.  Get beta 9.  Also check for whatever other zips you missed.

Why?  There is a flaw in the design of CWSDPMI beta 7 and earlier when
dealing with memory zones.  Each memory zone got it's own page directory.
DJGPP beta 4 uses a different memory zone for each sbrk(), so the memory
your program gets spread all over the place, and page faults page directories
like crazy.

Hey, all you beta 3 users, go ahead and upgrade CWSDPMI now, it won't hurt.  
But beta 4 will run slow and run out of VM if you don't!