X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 1 Sep 2010 14:37:18 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Cygwin slow on x64 systems Message-ID: <20100901183718.GD15157@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4C7B9327 DOT 9030204 AT graphtech DOT co DOT il> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Wed, Sep 01, 2010 at 05:12:19PM +0000, Magnus Holmgren wrote: >Magnus Holmgren gmail.com> writes: > >> I did some testing on my 64-bit Vista system, and it appears that >> CreateThread is the main cause. > >I think I've found the reason for the slow CreateThread. It seems like >the following remark in the MSDN documentation is relevant, at least for >WOW64 processes: > > * During process startup and DLL initialization routines, new threads can > be created, but they do not begin execution until DLL initialization is > done for the process. Which was precisely why sigproc_init was called there to begin with. cgf -- 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