Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>,
	<http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Date: Wed, 18 Aug 1999 09:55:04 -0400
Message-Id: <199908181355.JAA05968@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: brendan AT dgs DOT monash DOT edu DOT au
CC: cygwin AT sourceware DOT cygnus DOT com
In-reply-to: <37BA6550.F150BFFB@dgs.monash.edu.au> (message from Brendan Simon
	on Wed, 18 Aug 1999 17:48:32 +1000)
Subject: Re: Cygwin performance projections
References:  <37BA6550 DOT F150BFFB AT dgs DOT monash DOT edu DOT au>


> I was wondering what projections the developers have for Cygwin
> performance ?  What are the bottle necks ?  What kind of performance
> increases are expected in the next release (any idea when) ?

We're not planning any *major* performance work in the near future,
but I do see the occasional performance change checked in.  I think
two hits are:

* path conversions and stat()
* fork/exec overhead

Since the code functions properly, it gets lower priority than other
problems and projects.  This makes it a good candidate for
user-contributed patches.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com