X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Mark Geisert Subject: Re: fork() unbearable in VM guest Date: Mon, 16 Aug 2010 05:16:08 +0000 (UTC) Lines: 12 Message-ID: References: <4C68194B DOT 1070409 AT gmail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Daniel Colascione writes: > I'm running Cygwin in a fresh 32-bit Windows 7 VirtualBox guest (on an > OS X code) --- and performance is even more unbearable than usual: each > process spawned from bash takes about 800ms; on my Windows 7 64-bit box, > I get at least 8-9 forks per second. > > Any idea what could be wrong? You mean, besides the additional layer of emulation? You are comparing apples to oranges in more ways than one. ..mark -- 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