From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: DJGPP vs Cygwin
Date:	6 Nov 2002 12:08:00 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	19
Message-ID:	<aqb0n0$i0s$1@nets3.rz.RWTH-Aachen.DE>
References:	<3DC890CA DOT DFC6BE71 AT yahoo DOT com>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 1036584480 18460 137.226.32.75 (6 Nov 2002 12:08:00 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	6 Nov 2002 12:08:00 GMT
Originator:	broeker@
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

CBFalconer <cbfalconer AT yahoo DOT com> wrote:
> I believe the majority of the Cygwin slowdown is due to the slower
> loading (although the program is much smaller than under DJGPP)
> and slower console output handling. 

It's almost certainly the console output.  That's always been my main
quibble with Cygwin: working with cygwin bash is almost unbearable to
me, because terminal output is so unbelievably slow.  It feels like my
old 25 Mhz '386 running raw DOS, when it didn't have the video BIOS
shadowed to RAM --- when it's actually a 1Ghz Athlon running Win98.
It's almost painful to watch some 20 screenfuls of 'ls' or 'cat'
listing scroll by.

Morale: if want speed out of Cygwin, be very sure to turn off all
console output.  Or at least redirect it to a file or /dev/null if you
want useful performance figures of the compiler itself.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -