X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=0.1 required=5.0	tests=AWL,BAYES_00,FREEMAIL_FROM,SPF_HELO_PASS,T_RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
Message-ID: <29937002.post@talk.nabble.com>
Date: Mon, 11 Oct 2010 12:11:11 -0700 (PDT)
From: Nicole Hamilton <hamilton AT hamiltonlabs DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Re[2]: Slow fork issue - Win x64
In-Reply-To: <AANLkTimJe4Ly=7EpJmn2eBPY6Gs8PZ1Xhb45trtowdsp@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <1613876000 DOT 20080917204140 AT F1-Photo DOT com> <COL101-W1796553906F07DD5A0E579E64F0 AT phx DOT gbl> <1542859895 DOT 20080918134643 AT F1-Photo DOT com> <21561482 DOT post AT talk DOT nabble DOT com> <27607447 DOT post AT talk DOT nabble DOT com> <29929206 DOT post AT talk DOT nabble DOT com> <AANLkTimJe4Ly=7EpJmn2eBPY6Gs8PZ1Xhb45trtowdsp AT mail DOT gmail DOT com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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



Reini Urban wrote:
> 
> And native linux 64-bit bash has these:
> 
> rurban AT deblap:~$ while (true); do date; done | uniq -c
>     228 Mon Okt 11 20:12:51 CEST 2010
>     250 Mon Okt 11 20:12:52 CEST 2010
>     221 Mon Okt 11 20:12:53 CEST 2010
>     200 Mon Okt 11 20:12:54 CEST 2010
>     183 Mon Okt 11 20:12:55 CEST 2010
> 

True.  On the same MacBook where I get counts of about 80 with my csh under
Win7, I get counts of about 150 to 200 (sometimes higher) with bash under
OSX.

Threads are very cheap under Windows but process creation is quite a bit
more expensive than under Unix or Linux.  This is part of why you're getting
hammered so badly emulating fork (in addition to obvious problems of not
having access to the page tables, which will get worse with the larger
images of 64-bit applications.)  Your own application code runs at whatever
the processor speed is.  But the OS underneath will reward or penalize you
with its own performance characteristics, depending on how you use it.

Regards,
Nicole
-- 
View this message in context: http://old.nabble.com/Slow-fork-issue---Win-x64-tp19538601p29937002.html
Sent from the Cygwin list mailing list archive at Nabble.com.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple