delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2002/05/01/08:34:38

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <FE045D4D9F7AED4CBFF1B3B813C8533775DB90@mail.sandvine.com>
From: Ken Faiczak <kfaiczak AT SANDVINE DOT com>
To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: FW: trying to understand poor performance of make + cygwin on W2K
Date: Wed, 1 May 2002 08:34:07 -0400
MIME-Version: 1.0

I'm trying gain some performance for our build process (cygwin on win2k)
and have compared it to the same make on linux

If I completely build our tree (about 
then rerun the make from the top it takes 9.5 seconds on linux 

if I do the same test on the same machine running
(machine P3-500 512MB)
win2k +cygwin 1.3.9 +make (3.79.1)
it takes 3.5 minutes

so 210 seconds versus 9 seconds.
all its doing is recursing down the tree, testing the dependancies
and determining it has nothing to do, so its not compiling anything
its all make +cygwin, I think (ie no gcc invoked anywhere)

any ideas on what to try?
is this an issue with the cygwin fork() implementation??
is this as good as it gets

ken




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019