Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Sun, 29 May 2005 13:13:24 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Serious performance problems (new snapshot has some performance improvement) Message-ID: <20050529171324.GA26603@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <000b01c563c7$f4456f00$976d65da@DANNY> <4298F195.9090600@familiehaase.de> <20050529000152.GE3094@trixie.casa.cgf.cx> <20050529001846.GG3094@trixie.casa.cgf.cx> <20050529030523.GA10263@trixie.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050529030523.GA10263@trixie.casa.cgf.cx> User-Agent: Mutt/1.5.8i On Sat, May 28, 2005 at 11:05:23PM -0400, Christopher Faylor wrote: >On Sat, May 28, 2005 at 08:18:46PM -0400, Christopher Faylor wrote: >>I have an idea about how to work around this problem but I have to think >>about how dangerous it might be. Basically removing the signal handling >>wrapper around pthread_getspecific and pthread_setspecific. That may >>work ok but I have to think about worst case scenarios. > >I've semi-convinced myself that pthread_[gs]etspecific do not need signal >protection so I've released a snapshot which turns it off: > >http://cygwin.com/snapshots/ > >This version is about 2.7 times faster than cygwin 1.5.17 but it is still >not as fast as mingw. I don't think we're going to hit mingw performance >since there are still cygwin overhead issues involved. > >AFAIK, this is only going to provide a speedup for this specific case. >I don't think a general cygwin user is going to notice any improvement. Gerrit, if you have a chance could you confirm or deny if this change has any effect for you? cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/