From: Endlisnis <s257m AT unb DOT ca>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: MAJOR slowdowns in translating TP7 gfx code to DJGPP2
Date: Thu, 10 Sep 1998 18:10:47 -0300
Organization: NBTel Internet
Lines: 16
Message-ID: <35F84057.F852776@unb.ca>
References: <35F45C78 DOT 2257 AT post DOT tau DOT ac DOT il> <35F45F0C DOT 2243BDB1 AT unb DOT ca> <35F53FD4 DOT 4D03 AT post DOT tau DOT ac DOT il> <35F59B28 DOT 35138CF4 AT unb DOT ca> <35F73D38 DOT DD044556 AT cartsys DOT com>
NNTP-Posting-Host: fctnts10c71.nbnet.nb.ca
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

> >         Well, it is going to run twice as slow in 320x200x16bit mode (because there
> > is twice the memory to write to).  And it will run 9.6 times slower in
> > 640x480x64k mode (and 25 times slower in 1024x768x64k).
> That assumes that the speed of the program is proportional to the screen
> memory to be written, which is almost never the case.  Deciding what to
> draw is usually slower than drawing it.
	I doubt that would be the case at 1600x1200x24bit.  I agree that I
over-simplified it, but resolution has a BIG affect on the speed of your
program, if it didn't, then everyone would use the highest possible res.
-- 
     (\/) Endlisnis (\/)
          s257m AT unb DOT ca
          Endlisnis AT GeoCities DOT com
          Endlis AT nbnet DOT nb DOT ca